On Wed, 2013-02-13 at 16:15 -0500, Jason Millard wrote: > Hello. > > I've been using previous versions of HttpClient forever using the > JCIFSEngine. I wanted to give 4.2.3 a try to see if it solved my > issues, but unfortunately I'm having the same problems. > > I was able to turn on debug logging and compare outputs. It's almost > identical except for my final 200 vs 401 status code. Of course the > type 1, 2, 3 messages have different signatures. > > Since the messages have addresses that I don't really want public, I > was wondering the best way to get help debugging. > > 2013/02/13 16:09:22:817 EST [DEBUG] headers - >> User-Agent: > Apache-HttpClient/4.2.3 (java 1.5) > 2013/02/13 16:09:22:817 EST [DEBUG] headers - >> Authorization: NTLM xxxxxx > 2013/02/13 16:09:22:928 EST [DEBUG] wire - << "HTTP/1.1 401 > Unauthorized[\r][\n]" > 2013/02/13 16:09:22:929 EST [DEBUG] wire - << "Content-Length: 1539[\r][\n]" > 2013/02/13 16:09:22:929 EST [DEBUG] wire - << "Content-Type: > text/html[\r][\n]" > 2013/02/13 16:09:22:929 EST [DEBUG] wire - << "Server: > Microsoft-IIS/6.0[\r][\n]" > 2013/02/13 16:09:22:929 EST [DEBUG] wire - << "WWW-Authenticate: NTLM xxxxxx" > 2013/02/13 16:09:22:929 EST [DEBUG] wire - << > "MicrosoftSharePointTeamServices: 12.0.0.6520[\r][\n]" > > > Thanks, > -- Jason >
Hi Jason Only Wireshark packet captures would be meaningful given Wireshark's ability to decompose NTLM messages into more readable data structures. If you are not willing or able to publish those there is not really much we can do just having wire logs with all NTLM blobs stripped away. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
