when evaluating ignore rules, domain names aren't converted to IP addresses

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Invoke gnome-network-preferences
2. Select [Proxy Configuration] tab and set [HTTP proxy] in [Manual proxy
configuration].
e.g. http://proxy:8080
3. Select [Ignored Hosts] and put my network address in [Ignore Host List].
e.g. 129.158.0.0/16
4. Invoke /usr/demo/jds/bin/proxy
5. Type my local host in stdout.
e.g http://foo

What is the expected output? What do you see instead?
expected: direct://
actually: the proxy set in GConf

What version of the product are you using? On what operating system?
0.2.3

Please provide any additional information below.
libproxy does not have the feature to convert url to ip address

Original issue reported on code.google.com by ke.w...@sun.com on 16 Feb 2009 at 2:27

[GoogleCodeExporter]

There is an underlying performance problem here (1 extra DNS lookup per URL).  
This
could perhaps be added at a later point (with caching, etc), but I wouldn't 
want to
force the penalty on everyone.

Original comment by npmccallum@gmail.com on 25 Feb 2009 at 8:31

[GoogleCodeExporter]

Original comment by npmccallum@gmail.com on 25 Feb 2009 at 8:31

• Changed title: when evaluating ignore rules, domain names aren't converted to IP addresses
• Changed state: Accepted

[GoogleCodeExporter]

Original comment by npmccallum@gmail.com on 25 Feb 2009 at 8:32

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I just verified what Firefox does in a similiar situation:

- Enter a proxy address
- Enter a exception to 10.0.0.0/8
- Browse to a site (using DNS name) that resolves to an IP in 10.0.0.0/8 network

-> Firefox forwards this request to the proxy.

so libproxy does exactly the same.

Typical example: default exception always contain localhost and 127.0.0.0/8. If
resolution would be performed to decide if the exception counts, localhost would
never have to be listed.

So I'm not sure libproxy should actually go down the road and perform the 
(expensive
in respect to time) dns lookups.

Original comment by dominiqu...@gmail.com on 26 Feb 2009 at 3:02

[GoogleCodeExporter]

As the behaviour is consistent with other major implementations, we won't go 
down the
road of slow performance due to dns requests.

Original comment by dominiqu...@gmail.com on 27 Feb 2009 at 11:26

• Changed state: WontFix