Thanks very much for all that info. It helps eliminate many possible explanations.
Now here are some more questions for you. 1. what platform is your browser running on? Windows? Solaris? Linux? 2. Is your browser configured to use any proxy? If so, tell me all about that configuration. 3. It would be helpful to have the entire stream of bytes (decrypted) that the client and server exchange in that first https request and response. That is, to have the entire https request, the https response header, and the body of the https response. With that info, we could then a) examine the https response to see if there's anything in it that confuses mozilla, and b) setup a similar little https server (such as NSS's selfserv test program) and have it serve that same page, and see if we can reproduce this behavior. -- Nelson Bolyard Disclaimer: I speak for myself, not for Netscape
