LiveHosts icon

LiveHosts

by Aioros

v2.0.0 Updated Mar 29, 2022 57.78KiB
CWS
10K
Users
★ 3.30
40 reviews
#5375
of 207.1K
developer
#459 of 18.1K
⚠️Not updated in over 2 years

Description

LiveHosts is a Chrome extension that aims at providing a working (even if sub-obtimal) solution to a common nuisance that many web developers have to deal with every day. If you have multiple versions of your websites sharing the same host names on multiple environments, you often need to switch the assignments in your OS hosts file. Other extensions (like the life-saving HostAdmin) can help with the cumbersomeness, but changes to the hosts file usually take an inconvenient amount of time to actually affect the browser. Unfortunately, there is no way to make Chrome direct requests for a hostname to a specific IP without a standard redirect - you could set up a smart HTTP proxy, but it's often not possible or not convenient. This extension settles for a sub-obtimal approach: requests to the indicated hostnames are redirected to the chosen IPs with an additional Host header. The browser's address bar reflects this behaviour showing the hostname right after the IP (e.g. http://127.0.0.1/www.example.com/). The extension also tries to take care of all requests to either the IP or the hostname in a consistent way. Issues After the redirect, the user is effectively in a different domain that the one they expected. They may notice some functional differences: - depending on the server, parts of a web page referring to the site URL (like href and src attributes) could be different from the original - window.location has a different value that can potentially throw off JavaScript snippets - most Cross-Origin request won't work
LiveHosts screenshot 1

Reviews (12 cached)

★☆☆☆☆2024-06-14
Jem Peijnenburg

Doesn't work on chrome. Does work on Firefox: https://addons.mozilla.org/nl/firefox/addon/livehosts/. Can this extension be fixed on chrome? I will adjust my review if it works.

★☆☆☆☆2023-11-27
Olexander Rakov

Does not work on Chrome :(

★☆☆☆☆2023-08-25
Null Null

It's already been said in comments here, but this does not do what it says. It rewrites the URL and replaces the domain with the IP you specify. This is absolutely no good for servers doing SNI!

★☆☆☆☆2022-04-21
Fanatics Developer

It does not work as it rewrites your url to use the desired IP instead of the dns address. It does not work because when the browser tries to match the SSL certificate with the domain name they'll never match!!!

★☆☆☆☆2021-08-23
Robert Moore

This does not work as I was expecting. It simply changes the URL in the Address bar to the IP.

★☆☆☆☆2019-05-06
László Fodor (emul)

I'm not sure if I do something wrong or this extension is really not doing what it states. What I expect is that if there is a host test.dev which originally points to 1.1.1.1 and I want to try out another server with the same hostname then I add the new ip to the /etc/hosts like: 2.2.2.2 test.dev I tried the same with this plugin and all it does that it rewrites the URL of test.dev to 2.2.2.2 which makes no sense as it wont be caught by the same web server config

★★☆☆☆2021-05-04
Kenny Griffin

The concept is cool, but it doesn't work for me. Installed it on a Mac on the latest version of Chrome. I input the settings and saved them, no redirects happened.

★★☆☆☆2020-04-14
Luke Wayne

Hard to use

★★★☆☆2019-11-27
tague _

It's a nice concept, but it doesn't really work perfectly. Redirects break the system, so for example if I want to test a virtual host for "foo.mysite.com" on a local server 192.168.x.x, but the main page of "foo.mysite.com" specifies a redirect to "/login", for example, the mapping won't kick in again and it'll try to send me to 192.168.x.x/login without faking the hostname being used, so the virtual host doesn't end up being used. The same also happens with HTTP-to-HTTPS redirects.

★★★☆☆2019-10-07
Ellis Benus

I don't think this will work with WordPress on a Local Web server installation? B/c it's changing the URL to IPaddress/wp-admin the server doesn't recognize it. Is there a way to make this work with WordPress on a WAMP installation?

★★★☆☆2019-09-30
yw662

Guy, the behavior is incorrect. First of all <IP address> is not the same origin of <Hostname>. Chrome will consider the two sites in a totally different way. The request is correctly sent, and the server should work, but the thing is at the client side: Chrome does not work this way. Secondly it wont work with HTTPS. The certificate returned by the server is for <Hostname>, not for <IP address>. Surely it is still useful some way, but what I am really looking for is sth. that works exactly the same way /etc/hosts works.

★★★☆☆2019-07-29
Supertyp (999)

It doesn't work for me at all? I give it a real hostname and an internal IP number but what it does is it redirects me to http://<given IP number>/<given hostname> Sorry, this makes no sense at all.

Permissions (3)

Permissions

declarativeNetRequestWithHostAccess scripting Can inject scripts into web pages storage Can store data locally in your browser

Details

Version 2.0.0
Updated Mar 29, 2022
Size 57.78KiB
First Seen Mar 25, 2026