From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.5) Gecko/20011011 BuildID: 2001101117 I sit behind a proxy server that requires authentication. Somehow I lost my configuration, and I had "direct connection to internet". When I tried to access an external site, I was prompted for my username and password in the normal manner. When I typed this in, the browser looked like it was downloading the page, but once completed, simply showed the page that I was already on. I finally tracked this down to my proxy settings, and re-enabled my manual proxy configuration, which fixed the problem. This is a repeatable bug. In Netscape 4.7, I would have had a warning stating that I proxy authentication is required.. I think this was the contents of the page returned from the proxy server. Reproducible: Always Steps to Reproduce: 1. Require a proxy server that requests authentication. 2. All web traffic goes through proxy server for Internet access. 3. Set proxy settings to "direct connection to the internet". 4. Try to access a site. Actual Results: External page was not displayed, despite the browser looking like it was downloading said page. Expected Results: Displayed the error page returned from the proxy server. As I didn't have any proxy settings, it shouldn't prompt me for my proxy username & password.
Works fine for me. However, since this bug was reported, a newer version of Mozilla (1.0 RC1) has been released. Reporter, please can you check to see whether this bug is still present in a recent build (Moz1-RC1 or a new nightly build) and inform us? If not, can you please resolve this report?
Tested with: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9+) Gecko/20020424
Using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417 I still get a similar problem. Having "direct connection" set, and then trying to access this site, I was asked to "Enter username and password for proxy at\nUsername:". Having entered my credentials, I got an alert dialog box with a warning triangle icon and the message "The document contains no data." If I have my proxy settings set properly, the authentication dialog says "Enter user and password for proxy at <proxy hostname>\nUsername:". Note that all Internet traffic passes through this proxy server, it is a dual homed gateway. Therefore any attempt to access the Internet directly will still pass through the proxy server, and it will return a "401 Unauthorized", unless the appropriate HTTP header is sent in the request.
David: It sounds like you have two possible problems: 1- Your proxy settings mysteriously began to say "direct" in the prefs panel one day. 2- You get proxy auth when using direct. This problem is probably a result of your network configuration (if you hit a proxy server and get back a 407 <give me proxy auth> response, then we will throw up a dialog box.)
1) Correct, but it's not happened since 2) ISTM that there are better ways that Moz could handle it. In Communicator, if you didn't have a proxy server configured in your settings, and the browser saw a response requiring authentication, then it would display the response that it saw (usually an error message, saying I need to authenticate). Moz is trying to be clever and still allow me to authenticate, but once I do, it gives me the error "The document contains no data." Irrespective of how my network is configured Moz should cope one way or the other. Either allow me to authenticate and get the pages requested, or display the error and force me to configure my proxy server settings.
cc: darin I don't think mozilla is being "clever", I think there just pieces of http code that are reacting to what they get. Lets deal with each problem at hand. First, lets get your prefs.js lines that relate to networking/proxies. Lets see if your prefs panel is displaying direct when it might actually be using a proxy connection. "network.proxy.*"
Let's forget the first portion, it (resetting to direct) hasn't happened since I reported the bug. My network settings are fine, I simply reset them with the UI and everything is fine. However, if I manually switch back to direct (for the sole purpose of testing this bug), I get the errors as reported. I guess you guys need to decide what to do if the browser is not configured for proxy access, but is confronted with a HTTP response stating that authentication is required. Do you (a) simply display the text portion of the HTTP response within the browser (as Communicator 4 did) or (b) ask the user for his authentication credentials (as you do now) but getting rid of the error that pops up.
Okay, I think I have a correct summary now. (ugh. A transparent proxy that asks for auth.) I haven't done a lab reproduction, but setting to NEW +helpwanted.
Darin: since you are futuring this, can you look at this and comment on the validity? (no point in futuring something if invalid...)
without a packet trace it's difficult for me to say if this bug is valid or not. there's a very good chance that the proxy server is not behaving as well as it could, but i can't know that without understanding what is actually passing between mozilla and the proxy server. dave: can you use a tool like www.ethereal.com to capture network traffic on port 80? the tool is not exactly user friendly, but if possible it would seriously help us understand how to resolve this bug. thx!!
So I've captured the proxy jumping in and asking for authentication, and the next HTTP request had a valid username/password. There were approximately 8 of these HTTP requests before Mozilla popped up a dialog box saying that the data is empty (or something like that). My firewall will not let me post the trace file up so I will email it privately to Darin, CC to BenC. It's a small file in tcpdump/libpcap format. FWIW this is regression from Communicator 4.
do you still have the issue with 1.4 ?
-> default owner
WFM with both Firefox 3.0.11 and Firefox 3.5.1 (on Windows XP Pro SP3).