Gareth Watts wrote:
My favourite tool for debugging HTTP requests is Charles Proxy: http://www.xk72.com/charles/ - Runs on Windows, Linux, OS X
Gives you a true view of what's going on as it sits between your web browser and the web server, intercepting all of the traffic flowing between them and letting you view every element of the request and the response.
Thanks for this; I've installed it to play with. It's Java based and doesn't seem to like anything other than Sun's jvm, but I got it working in the end!
It overcomplicates things by treating http://www.mysite and https://www.mysite as different sites making it hard to track the sequence between them, which seems odd. It also is showing me 301 (permanent redirect) responses but unless I'm missing something seems to not be telling me where the redirect destination is. My suspicion is that there's something wrong in the response that's not giving a complete answer and therefore getting the browser to "guess", and the browser is guessing wrong. It would just be nice to see the actual response to be sure!
Nonetheless a useful tool even if it won't solve this problem. I could have used this hundreds of times in the past.
[Later:] I just noticed that in preferences I can tell it not to merge headers with content, and that now shows me the full response headers.