- When Proxy-Authorization is required, Mozilla does not "remember" to send the Proxy-Authorization header. What happens is that Mozilla sends a request to the proxy (without any Proxy-Auth headers), the proxy responds with a Proxy-Authenticate: and Mozilla closes the connection (HTTP/1.1 proxy), and repeats the request with a Proxy-Authorization header. This happens for each connection. In other words, I load a page with 10 images, Mozilla performs the proxy-auth challenge business for each of the 10 connections! Previously it would only do it for the first connection attempted, and remember to send the Proxy-Authorization header with all subsequent connections unless the proxy preferences are changed.
- Keep-Alive connections to proxies do not work as desired. I'm happy
that keep-alive does work again (for the last few months with a HTTP/1.1
proxy mozilla would close the connection after every request -- that's fixed,
thank you). However, mozilla still closes all open connections after
loading each page. i.e. it treats keep-alive connections to the proxy as
if it were talking to the server. I have a proxy that tries to keep-alive
as many connections to the browser as possible to improve speed, but mozilla
closes them all when it's done with a particular page, despite the proxy
sending keep-alive headers. It appears that mozilla keeps the connection
open until the next page is loaded, at which time it closes all open
connections and opens a bunch of new ones for the new page.
--Bob
