Firebug 2.0+ Causes extra get request on page

42 views
Skip to first unread message

Melyssa St-Hilaire

unread,
Jul 16, 2014, 1:45:42 PM7/16/14
to fir...@googlegroups.com
I used to have this problem with a much, much older version of Firebug (we're talking over a year ago, if not 2), and I think YSlow being active (it is not right now, I even uninstalled it completely) but it had gone away and the last 1.x version (1.12) is not causing any issues. However ,whenever I update back to 2.x it does it again.

Basically what it does is it will cause a second GET request to the page I just loaded. I work on an ASP.Net application that is somewhat old, and a LOT of the navigation is based off of session variables and postback chain (yes, I KNOW that's bad. I did not write the original code - it was an ASP app that was transfered to .Net and we've been patching it for years because of time and money contingencies. I would rewrite the whole thing if I could, trust me). That extra get request resets everything and makes it nigh impossible to debug the javascript in firebug since I can never stay where I need to be. (I can SEE the extra request in the trace.axd file being done about 2 seconds after the inital page load is done)

I looked up on google a few similar issues that had something to do with img tags with an empty src causing the extra request with new version of FIREFOX, not firebug. However, FF without firebug activated doesn't give me grief.

Is there a feature I can disable to stop this from happening? Any chances that might get looked into? At the moment I resolved to going back to version 1.12 and turning off auto updates since I'm not a huge Chrome fan (and I hate IE with a passion, not that its debugger is of any use, either way), but it would be nice to be able to update at some point.

Thanks.

Simon Lindholm

unread,
Jul 17, 2014, 4:40:22 PM7/17/14
to fir...@googlegroups.com
Try using the XPI from https://code.google.com/p/fbug/issues/detail?id=7401#c14 with the Net panel enabled (the patch will also be in the next release, if you prefer to wait). The underlying problem is that Firebug 2.0 started making additional requests for the Script panel, rather than intercepting all requests, for reasons of performance and as part of switching to a new debugger service.

/ Simon
Reply all
Reply to author
Forward
0 new messages