What would be a good option to troubleshoot an interaction of browser with a server besides wireshark?
I mean being able to see what the browser sends and receives.
Is firebug a good alternative or is it only for
css and the
closed as not constructive by Michael Hampton♦, MDMarra, joeqwerty, Shane Madden♦, gWaldo May 16 '13 at 19:22
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.
If you're looking for something HTTP specific, I recommend Fiddler2. It dissects HTTP traffic in very useful ways, does HTTPS decryption, supports Firefox and IE, and can even resend previous HTTP requests or modify them before resending.
To name a few you can try, Ettercap and Kismet are good CLI based sniffers too.