Hosts file through a proxy

[rama]

Hello,

I have this question, I'm working in a lan with several computers, those
computers have access to the Internet through a Proxy, so that in the
Internet explorer the settings are that I use a proxy. This works fine.
However when I tried to acces the adreess 127.0.0.1, the browers doesn't
find this address, although in my hosts file there is this entry " 127.0.0.1
localhost"

I'm asking this because I wanted to block access to certain pages using the
"127.0.0.1 WWW.****.***", which doesn't work either.
I tried clicking the "don't use proxy for local addresses" but it doesn't
work either.

Any idea how can I solve this problem, I`m not an expert in case you haven`t
noticed

thanks

 

[Herb Martin]

Hello,

I have this question, I'm working in a lan with several computers, those
computers have access to the Internet through a Proxy, so that in the
Internet explorer the settings are that I use a proxy. This works fine.

However when I tried to acces the adreess 127.0.0.1, the browers doesn't
find this address, although in my hosts file there is this entry " 127.0.0.1
localhost"

What happens when you go to the command line
and type:

ping www.blockedname.com

This will bypass any IE specific proxy settings.

Probably a missplaced file.

I'm asking this because I wanted to block access to certain pages using the
"127.0.0.1 WWW.****.***", which doesn't work either.

Host files don't support wildcards.

Host files do support specific names.

Likely you have missplaced (wrong directory) or
otherwise mangled your Hosts file.

%systemroot%\system32\drivers\etc\hosts

(No file extension, text only.)

I tried clicking the "don't use proxy for local addresses" but it doesn't
work either.

That happens AFTER the name resolution.

 

[Phillip Windell]

I'm asking this because I wanted to block access to certain pages using the
"127.0.0.1 WWW.****.***", which doesn't work either.
I tried clicking the "don't use proxy for local addresses" but it doesn't
work either.

Of course it doesn't. 127.0.0.1 is the machine you are sitting at. It
probably has no webserver running on it,...how is it going to go to a site
on a server that doesn't exist?

127.0.0.1 is *always* the machine you are sitting at.

 

[Herb Martin]

Of course it doesn't. 127.0.0.1 is the machine you are sitting at. It
probably has no webserver running on it,...how is it going to go to a site
on a server that doesn't exist?

That is the point of these tricks that mask out a particular
name -- they typically use 127.0.0.1 (or any other quick,
non-web server address) to return an error.

 

[Phillip Windell]

That is the point of these tricks that mask out a particular
name -- they typically use 127.0.0.1 (or any other quick,
non-web server address) to return an error.

Ok, I misunderstood what he was wanting to do.