213290 - Proxy: HTTP needs DNS resolution

Status: VERIFIED INVALID

(Core :: Networking: HTTP, defect)

Description

[Baptiste SIMON]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.1; Linux)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.2.1) Gecko/20030225

Mozilla can't open web pages if it is configured to use a proxy and if there is no DNS on the 
network. Typpically, in a closed network w/ only a simple web proxy and no DNS forwarder, 
you cannot connect to any website. 
 
Nota: you don't _need_ DNS resolution w/ proxies 

Reproducible: Always

Steps to Reproduce:
1. go into a closed network opened on the web only through a web proxy... which doesn't 
provide any DNS server (or "# > /etc/resolv.conf") 
2. configure mozilla to use the proxy 
3. wait and see the DNS resolution failure and the global page loading failure 
Actual Results:  
global loading failure when requesting any web page which URL cannot be resolved 

Expected Results:  
We would expect that mozilla would let the web proxy resolv the DNS domain name and bring 
us the requested web page

Comment 1

[Jo Hermans]

Bug 136789 wants the opposite !

Comment 2

[Olivier Cahagne]

can you try the special build mentioned here:
http://weblogs.mozillazine.org/darin/

Comment 3

[Darin Fisher]

>Nota: you don't _need_ DNS resolution w/ proxies 

yes, you do.  you need to resolve the proxy server host name.  other than that
you are correct.  can you provide a HTTP log for this bug?  here's some
instructions:

  http://www.mozilla.org/projects/netlib/http/http-debugging.html

thanks!

Comment 4

[Baptiste SIMON]

> you need to resolve the proxy server host name

of course... I'm not talking about disabling ALL DNS resolutions... I just want
Mozilla not try to resolv host of distant web sites if it goes through a proxy
server.

I'm sorry, I can't do lots of things for this bug, work is waiting me. :c(

Comment 5

[Darin Fisher]

>Mozilla can't open web pages if it is configured to use a proxy and if there is
>no DNS on the network.

so, if you enter a numeric ip address for the proxy host name, then things
should work.  you should not need to have a DNS server on the network.  but, if
you want to enter a non-ip address as the proxy host name, then you need to have
a DNS server.  are you saying that you are entering a numeric ip address for the
proxy server, and mozilla is still requiring a DNS server?

Comment 6

[Baptiste SIMON]

> are you saying that you are entering a numeric ip address for the proxy
server, and mozilla is still requiring a DNS server?

yes, and that's the matter.

I've noticed something crasy :
- try connecting through the proxy (w/out DNS server) on HTTP, it fails on
  the DNS resolution
- try connecting through the proxy (w/out DNS server) on HTTPs, it goes
  towards w/out any problem on the DNS resolution. :c/

bye

Comment 7

[Darin Fisher]

Baptiste: tell you what.. without the log file i requested in comment #3, it is
going to be nearly impossible for us to get to the bottom of this bug.  if you
have the time to produce the log file that would be excellent.  if not, then i'm
not sure what we can do about this bug :-/

Comment 8

[Baptiste SIMON]

ok :c)
I hope I would find the time to do that... I leave this environment soon
(tomorrox). maybe tomorrow I'll find time....

Comment 9

[Darin Fisher]

Baptiste: so, any more info?

Comment 10

[Baptiste SIMON]

arf... strange thing to be named "Baptiste" on the net ;c) used to be named
"BeTa" ;c)

so... I don't have access to this environment anymore. :c(( that's why I haven't
posted more information. It was during a job, and I didn't have enough "free" time.

The only things I can tell are :

- Surfing on HTTP w/out DNS name resolution capabilities was impossible
- Surfing on HTTPs w/out DNS name resolution capabilities worked really well

don't tell me why... :c/

I have to add a something : theorically, surfing w/ proxies doesn't make us
needing name resolution.

good luck :c(

Comment 11

[Darin Fisher]

marking INVALID...

BeTa: not enough info really for a bug report.  no place at all to begin
searching for a solution.  i understand that you have no way of getting more
info from your previous setup, but if by chance you encounter the same problem
elsewhere, please do let us know.  thanks!

Comment 12

[Baptiste SIMON]

Of course... if the same configuration is reproduced, be sure you'll have more
information. thanks for your work.

BeTa ;c)

Comment 13

[benc]

Darin: I'll probably have my logging DNS server working soon, so I could try to
do the HTTP log and have server log data as well.

However, I'm wondering if this is really worth analyzing. If you think it is
important, let me know. Otherwise, this will remain pretty low on my list.

Comment 14

[benc]

V/invalid.

I've got tracing working, and I don't see any DNS activity when proxy is on,
EXCEPT to lookup the proxy server name.