Closed Bug 102707 Opened 23 years ago Closed 23 years ago

all content behind http auth requested twice

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: jmd, Assigned: darin.moz)

Details

I have a page I access via HTTPS that requires basic http authentication to access anything, including /. I notice in the logs for each object it requests, it first tries without sending the authentication information. Then it seems to wait a noticable amount of time before rerequesting with the auth info. 1.3.8.1 - - [02/Oct/2001:12:59:26 -0500] "GET /img/foo.jpg HTTP/1.1" 401 523 1.3.8.1 - user [02/Oct/2001:12:59:31 -0500] "GET /img/foo.jpg HTTP/1.1" 200 44626 Especially since HTTPS pages aren't being cached, this causes pages to be very slow to load, compared to IE.
-> http
Component: Networking → Networking: HTTP
QA Contact: benc → tever
Assignee: neeti → darin
-> darin. Is this a dupe?
reporter: can you provide a testcase?
Unfortunatly I can't. The only https+httpauth site i know of is a private intranet.
tever: can you reproduce this bug with a local setup?
Keywords: qawanted
reporter, can you please generate a HTTP log file and attach it to this bug? steps to do so can be found here: http://lxr.mozilla.org/seamonkey/source/netwerk/protocol/http/src/nsHttp.h#36 this can be done using a nightly build.
Well, something must have changed in the cache. HTTPS objects are now being cached, and only requested once, with the auth info. Much faster switching between pages now, since they all have the same 15 images at the top. Tested with 2001101808 (linux)
reporter: what build were you originally testing... there was a bug a while back that caused each request to be tried first without authentication credentials, and then to be repeated with the stored authentication credentials upon failure. this extra request for each authenticated URL would not be seen by the user, but would noticeably slow down page load performance. so, perhaps your original report is a dupe of that bug? ... which has been fixed for some time. either way, marking WORKSFORME per reporter's comments.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
The original build was quite likely reported with a current build, no more then 2-3 days old. So assume a build right around the report date, 2001-10-02. If it was fixed previous to that, perhaps it regressed and disapeared again silently.
hmm.. that would be after the fix i was refering to, so if it turns up again, please reopen this bug. thanks!
Verified WFM.
Status: RESOLVED → VERIFIED
QA Contact: tever → junruh
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.