Custom Ports / Extension Doesn't Work?

[own3mall]

When I map site.com to an IP of 1.1.1.1 (for example), when I try to access https://site.com:21222, it doesn't work. This extension doesn't do the same thing that a hosts file entry change does?

Also, why are the URLs sometimes changed to https://1.1.1.1:21222/site.com in the address bar? This is not correct?

I just get a message of:

The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    This problem can sometimes be caused by disabling or refusing to accept cookies.

However, if I create a hosts file entry of 1.1.1.1 for site.com, everything works as it should. Does this extension support custom ports? Does it work with any possible redirects setup on a domain too?

[Aioros]

Hi @own3mall, as described in the README, the extension does not in fact do the same thing that a hosts file change does, at least not perfectly. As far as I know, that's not possible in a browser extension at the moment (unless the APIs changed a lot in the last few months). What it actually does is, it sends the request to the specified IP with the Host as an HTTP header.

The url is visually changed to give the user an idea of where he actually is. The port being there should not (in theory) be a problem, but I'll check. Thanks for reporting your issue.

[own3mall]

I'm starting to think this isn't a bug. Rather, it's weird behavior coming from WordPress (it sends redirect 301 headers that are weird).

I got it working by setting up two strange rules (I'm using a real URL and different port than what is used in my examples):