On Oct 7, 5:28 am, John J Barton <[email protected]> wrote: > Yes, please help me understand what a NTLM is.
In short, NTLM is a Microsoft authentication protocol that is used in their products for single sign-on, so that the "Windows" login may be used for transparently logging in to web sites. NTLM is used extensively in large corporations for intranet sites and similar, and is widely implemented in web browsers from other vendors, including Firefox. Overview: http://en.wikipedia.org/wiki/NTLM Gory reverse-engineering details: http://davenport.sourceforge.net/ntlm.html Fetching a resource over NTLM means doing three requests: GET /index.html HTTP/1.1 401 Unauthorized ("I want NTLM" in header) GET /index.html (NTLM Type1 message in header) HTTP/1.1 401 Unauthorized (NTLM Type2 message in header) GET /index.html (NTLM Type3 message in header) HTTP/1.1 200 OK (resource fetched) so seeing the first block of the script being repeated three times doesn't seem like a coincident. I guess the two body-less 401 responses incorrectly lead to writing copies of the first 4KB to the internal resource buffer. (Note that Firefox view source gets it right so this a Firebug problem) The following Firebug issues describe other dimensions of this problem: http://code.google.com/p/fbug/issues/detail?id=1902 http://code.google.com/p/fbug/issues/detail?id=1927 Just let me know if there's anything else I can do to help Mike -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
