dns – How to redirect from subdomain to another port without showing IP on browsers address bar?

I tried to add another service on the same server with a different port, I found that in Cloudflare, we should use a record with page rules to redirect this subdomain to an IP address with a specific port.

The problem is that when Cloudflare redirects users to another port service, it displays my server's IP address in the browser's address bar instead of displaying the subdomain.
Is there anything I can do to hide this IP address by URL on the client's browser?

html – Irregular font size in browsers of some Android devices

In the following HTML document:

http://fiddle.jshell.net/v0yqL8xp/show/

When running on an Android device> = 8 and a Chrome browser (79.03945.116), I find the following problem related to the font size (font-size: 16px;):
The two divs of the .medium class reduce the text compared to the .large class
If I increase the size of the .medium class to 100%, the text returns to the correct size.

Has anyone had similar problems?

HTML and CSS: http://jsfiddle.net/v0yqL8xp/

Extract:

*
{
	padding: 0;
	margin: 0;
}


.medium
{
	float: left;
	width: 50%;
}

.large
{
	width: 100%;
}

p
{
	text-align: justify;
	font-size: 16px;
	padding: 14px;
}

Fugiat sit et tempor magna adipisicing excepteur veniam. Velit reprehenderit amet do et sint officia Lorem esse irure eiusmod consectetur. Laboris esse duis enim dolore et ex aliqua proident ullamco id ullamco nostrud amet. Qui culpa ad sint adipisicing do cillum velit proident exercitation ipsum. Pariatur reprehenderit reprehenderit elit irure ea cupidatat labore minim. Labore qui est minim occaecat commodo minim consectetur id aliquip. Sit veniam excepteur cupidatat eiusmod.

Fugiat sit et tempor magna adipisicing excepteur veniam. Velit reprehenderit amet do et sint officia Lorem esse irure eiusmod consectetur. Laboris esse duis enim dolore et ex aliqua proident ullamco id ullamco nostrud amet. Qui culpa ad sint adipisicing do cillum velit proident exercitation ipsum. Pariatur reprehenderit reprehenderit elit irure ea cupidatat labore minim. Labore qui est minim occaecat commodo minim consectetur id aliquip. Sit veniam excepteur cupidatat eiusmod.

Fugiat sit et tempor magna adipisicing excepteur veniam. Velit reprehenderit amet do et sint officia Lorem esse irure eiusmod consectetur. Laboris esse duis enim dolore et ex aliqua proident ullamco id ullamco nostrud amet. Qui culpa ad sint adipisicing do cillum velit proident exercitation ipsum. Pariatur reprehenderit reprehenderit elit irure ea cupidatat labore minim. Labore qui est minim occaecat commodo minim consectetur id aliquip. Sit veniam excepteur cupidatat eiusmod.

javascript – classList fallback (IE and older browsers) – good enough?

I'm trying to make it JS code more compatible with the browser.

So i wrote an alternative to JS& # 39; s classList provide her .add(), .remove() and .toggle() functionality because it is not or simply partially supported in IE.

(I know there are existing polyfills, but I like having a good overview of my code)

My test was successful, but before using it extensively, I wanted to check with someone if he saw any problems.

the code is:

    function classes(type, element, targetClass){
            var classArray = element.className.split(/s/);
            var index = classIndex(classArray, targetClass);
            // if target class is in class list
            if(index !== null){
                // multiple classes
                if(classArray.length > 1){
                    if(type == "remove" || type == "toggle") {
                        classArray.splice(index, 1);
                        element.className = classArray.join(" ");
                    }
                }
                // single class
                else {
                    if(type == "remove" || type == "toggle") {
                        element.className = "";
                    }
                }
            }
            // if target class is not in class list
            else {
                if(type == "add" || type == "toggle") {
                    element.className += " " + targetClass;
                }
            }
            // check if target class is in class list (returns index or null)
            function classIndex(array, targetClass){
                for(i=0; i

use:

classes("toggle", myElement, "classToToggle")

thanks in advance, Andy

bip44 – Testnet addresses fail in browsers

I have generated a testnet address like this:

const btc = require('bitcoinjs-lib');
const bip32 = require('bip32');
const bip39 = require('bip39');

var root = bip32.fromSeed(
    bip39.mnemonicToSeedSync('my-twelve-word-seed...'), 
    btc.networks.testnet
);
var pubkey = root.derivePath("m/44'/1'/0'/0/0").publicKey;
console.log(btc.payments.p2pkh({pubkey}).address);

and for my troubles I end up with this value: 14kwGTShacA5hT4uAes7dkNvreuHXuRRf7

however, when I test this with BlockCypher (or Blockchain.com or another explorer), it doesn't seem to recognize it:

curl https://api.blockcypher.com/v1/btc/test3/addrs/14kwGTShacA5hT4uAes7dkNvreuHXuRRf7/balance

returns

{"error": "Address 14kwGTShacA5hT4uAes7dkNvreuHXuRRf7 incompatible
with the current blockchain: BTC.test3 "}

note that according to BIP44, the bypass path for testnet parts is m/44'/1' against. m/44/0' for mainnet

so what's wrong here?

CSS button effects do not work on all browsers

Having some problems with the effects of a CSS button does not work on all browsers.

It appears the way I want it in Chrome, but not in Firefox.

I can't seem to find the root of the problem. Here's what I have.

Violin
SEMrush

Button

Code (markup):

a.soft {display: inline-block;font-family:'Varela Round', sans-serif;padding:2rem3rem;font-size:1.25vw;box-shadow:-10px-10px20px0#E6E6E6,10px10px20px0#ABABAB, inset 10px10px20px0#E6E6E6, inset -10px-10px20px0#ABABAB;border-radius:50px;transform: box-shadow 1s ease-in-out;background-color:#666666;-webkit-background-clip: text;color: transparent;text-shadow: rgba(245,245,245,1.0)2px2px5px;font-weight: bolder;}

a.soft:hover {background-color:#ddd;box-shadow:-10px-10px20px0#E6E6E6,10px10px20px0#ABABAB, inset 10px10px20px0#E6E6E6, inset -10px-10px20px0#ABABAB;color:#888;}

a.soft:active {box-shadow:0020px0#E6E6E6,0020px0#ABABAB, inset 0020px0#E6E6E6, inset 0020px0#ABABAB;color:#D8D8D8;text-shadow:1px1px2px white;-webkit-background-clip: text;font-weight: bolder;}

Code (CSS):

Why have browsers chosen to implement HSTS with Preload rather than checking custom DNS information?

Browsers and standards organizations prefer HSTS over Preload because it avoids sending an http request to a website that supports https. That's good, because plain text http requests can be intercepted to configure Man in The Middle attacks.

But a number of websites explain that a centralized preloading list doesn't adapt well to the mainly https web that has been offered by the W3C, EFF and others. Managing a centralized list creates a bottleneck for finding, adding, and deleting list items.

However, this technology has been implemented rather than, for example, using DNS, which is already well distributed and is already used by browsers to search for URL domain names.

Of course, the DNS is not yet secure and the proposals to secure it are controversial. But why should the DNS be secure to hold one more bit of information (if the domain can support https – and ONLY https – or not)?

In the worst case scenario, a malicious MiTM attack could give the impression that a website is not secure when it is actually secure. But in this case, an insecure connection would simply fail. This failure would deprive the malicious user of any benefit.

So naturally, I wonder why a centralized HSTS with preloading is preferred to adding a new flag to DNS zones to indicate that the domain supports https connections.

nginx – The site is accessible by domain in all browsers except Chrome

I'm trying to create a website with the help of an Ubuntu machine running nginx. For some reason I can access the site by domain name in Safari and Firefox, but in Chrome it can not access the server. However, I can use curl, postman, etc. and I get the index.html file as I would like.

I've found that in Chrome, I am able to access the site using the IP address, and I am totally lost on where to check next.

Here is my configuration file:

server {
    listen 80 default_server;
    listen [::]:80 default_server;

    root /var/www/html;

    index index.html index.htm index.nginx-debian.html;

    server_name _;

    location / {
            # First attempt to serve request as file, then
            # as directory, then fall back to displaying a 404.
            try_files $uri $uri/ =404;
    }

}

I've changed the response code just to make sure it's all about the setup I'm actually typing.

Any help would be appreciated!

Edit: The domain is gwilliam.dev

Your site on different browsers | Promotion of the forum

I'm still testing my forum after an upgrade or a theme change with different browsers and sizes. The main browsers with which to test would be Internet Explorer, Microsoft Edge, Mozilla FireFox, Google Chrome and Mobile Safari. I have not noticed any problem with any of them. :]

tls – Why are file URLs marked as unsafe while https URLs are marked as secure in browsers?

I think file protocols are more secure than https protocols.

You would be right if the file comes from a local storage.

What happens if you load a file from an FTP mount (the FTP protocol is not secure, even the passwords are sent in plain text)? Or from a remote service (unsecured) on an unencrypted wifi network? A consumer access point with a connected drive could be configured like this.

The browser has no way of knowing if any of these connections is really secure. And even though it was possible to determine if the file system's direct links were secure, we can not know if the next step in the chain is.

So the browser just does not guarantee what it does not know.

html – Browsers ruin the UX password with drop-down menus. How can I fix it?

drop-down list of autofilling ruining UX

FYI The picture above was taken with autocomplete="new-password"

As you can see, the drop-down list covers the error message (which ends with "letters and numbers" (plus some other error messages).

This error message is IMPORTANT, and the user MUST see it. How to hide the drop-down list? The drop-down list prevents the user from seeing the message. You can say that "the drop down menu is bad UX" in this particular circumstance

You can say to move the message under the field, but then we have the exact same problem, just in the other way.

As far as I know, our solutions are:

  1. disable the drop-down menu
  2. move the message to a place where the drop-down menu will not cover it (like a popup or sideways)
  3. Move the message so that it is always displayed on the opposite side of the drop-down menu.

Option 1 does not work because we could disable the drop-down menu by setting autocomplete at "new-password" or "off" or "false" or something else, but none of this seems to disable the drop-down menu.

Option 2 does not really work because I want the message to be near the field to give some context to the error message. I do not really want to popup with the error message "Your password is too short" as it looks like a bad UX. I imagine that I could move the error messages to the input side of the password, but that would not work on small devices that do not have the width of the ######################################################################### 39; screen.

Option 3 also does not seem very good, because the error message moves according to the scroll position of the window, and move text according to an arbitrary scroll line also seems to be a bad UX.

So yes, I am short of options, unless someone can think of one of them?

Is this a browser problem? Or is there a simple trick I can use to get the right UX I want?