From Bugzilla Helper: User-Agent: Mozilla/4.72 [en] (WinNT; U) BuildID: 2000073008 When an HTTP 304 response code is received, the original headers associated with that request are not redriven to the HTTPNotify AsyncExamineResponse listener/observer. I'm working on the Platform for Privacy Preferences (P3P) which requires that I see those original response headers since P3P uses response headers as part of it's protocol. Reproducible: Always Steps to Reproduce: 1. Visit a site for the first time. 2. Return to the site receiving a 304 HTTP response. Actual Results: Only the response headers from the 304 response are sent to the AsyncExamineResponse HTTPNotify listener. Expected Results: The response headers from the 304 response should be sent to the AsyncExamineResponse HTTPNotify listener. Then, the AsyncExamineResponse HTTPNotify listener should be redriven with the original headers. Below and attached is a diff with a change that I made to nsHTTPChannel.cpp to cause the redrive of the original headers. Index: nsHTTPChannel.cpp =================================================================== RCS file: /cvsroot/mozilla/netwerk/protocol/http/src/nsHTTPChannel.cpp,v retrieving revision 1.213 diff -r1.213 nsHTTPChannel.cpp 2355a2356,2357 > OnHeadersAvailable(); >

-ruslan

Are you sure that's the right thing to do? Just trying to look for sideffects ....

pulling in ruslan's necko bugs ->darin

http bugs to "Networking::HTTP"

my changes for bug 76866 will fix this bug as well.

fixed with branch landing

verified