Difficulty tracing IE 6.0 bugs, tools?
I have been using a tool call proxyTrace 0.1.2.23 to look at the web traffic to the web server. But in the web log it does for every submit I get a HTTP Server Status Code of 500, follow by a 200. I'd like to see the complete truth (both accesses listed in the trace tool) but instead I get the half truth (the completed access, with the incomplete access omitted completely). Anyone know how other Windows or Linux tools thats helpful in seeing the conversation going between the web client and the web server? Many many thanks!
We need more information. Which server are you using? IIS? Apache? Version?
proxytrace is a cool tool, but it has some bugs in it which is probably what you're seeing.
I *highly* recommend the Ethereal network sniffer. It can parse many network protocols into user-friendly data. It's open-source, too.
It's funny you mentioned ethereal, I installed it and nothing
Don't forget to install the pcap library. It won't work without it.
another vote for ethereal. Ive been impressed with it ever since I first installed it.
Only beef i have with Ethereal is its shitty UI. It's absolutely horrendous. I know, I know.. it's probably needed for cross-platform compatibility, but that doesn't make it better, tho'.
I tried it again today, and got it working. I found I could list the packets life with the right optoins in the Start dialog box. And there are some neat things you can do to list the actual text being passed around (the hex pane is kinda useless). Plus had it doing what I wanted to do. Got the filter to do "(ip.src eq my.ip.xx.xx) or (ip.dst eq my.ip.xx.xx) and (tcp.port = 80)" or something like that.. exactly what I needed. There are all kinds of niceties: It shows all the related syncs and acks, and I haven't even started using the logging facilities or command options, very nice! :-) I'll have to get used to Richard Steven's level of comfort though. That man was able to parse this kind of stuff in his sleep.
Fog Creek Home