186313 - HTTP auth in URL is inconsistent with relative URLs

Status: RESOLVED EXPIRED

(Core :: Networking: HTTP, defect)

Description

[Neale Pickett]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5

When traversing certain links using HTTP auth information in the URL itself,
some links seem to cause Mozilla not to send authentication.  But if you press
reload, or navigate back then forward, the credentials are sent.

I'm having trouble explaining this.  Check the steps to reproduce :)

Reproducible: Always

Steps to Reproduce:
1. Load up
http://bugzilla%40mozilla.org:[e-mail]/~neale/albums/2002/index.html
2. Click "2001" on the left, you should be asked to authenticate.
3. Click the Cancel button
4. Click Reload, now the page displays
Actual Results:  
At step 2, no authorization is sent, nor is any attempted.  At step 4, the
authorization in the URL is sent.

Expected Results:  
Mozilla should have sent the authorization with the load of the page in step 2.

I haven't tested extensively, but it seems like this only happens when .. is in
a relative URL.

Comment 1

[Neale Pickett]

I recently removed the username/password combo described in this bug, but I have
just now added it back.  I can still reproduce this bug using Linux Firefox 0.8
(from Debian testing).

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.