search

firebug / firebug

Web Development Evolved - The Firebug you have known and loved
http://getfirebug.com/
1.35k stars 343 forks source link

Net Response tab incorrect #2878

Closed fbugissues closed 9 years ago

fbugissues commented 9 years ago

Originally reported on Google Code with ID 2739

The Net Response tab was working correctly, but not on 1.5 anymore.

The problem is that *all* code from previous request for the same url are
being outputted in the response tab.

What steps will reproduce the problem?
1. Have a site which will return *something* for a certain call (my url
was: http://url/index/#start)
2. Do a XHR for the same url (my url was: http://url/index/#line) 
3. Look in the Net XHR Repsone tab. Now I see the following: For the first
request I can see the response returned for that specific request. In the
second request I can see them for *both*!

Since my first request gets a full html website, and my second only some
small additional information, it's very annoying that now I see both the
long HTMl listing, needing to scroll all the way down, to look at the
actual response.

For example, the 'repsonse' for my second call is (according to FB 1.5):
--------------
<!DOCTYPE html PUBLIC ...... cut out some html .......</body></html>"intro"
-------
While only the 'into' part is the actual response.

In all the previous firebugs this worked correct on MAC and Windows.

Reported by olaf.kwant on 2010-01-21 14:35:28

fbugissues commented 9 years ago 
Yes, I can reproduce that.

Test case available here (online in 30 minutes):
http://getfirebug.com/tests/issues/2739/issue2878.html

Honza

Reported by odvarko on 2010-01-21 15:28:54

fbugissues commented 9 years ago 
Patch committed at R5776
Will be in Firebug 1.6a4 and backported in Firebug 1.5.1

Thanks for the report!
Honza

Reported by odvarko on 2010-01-22 11:04:34

fbugissues commented 9 years ago 
Thanks for reporting this bug. It is one of 25 issues fixed in Firebug
1.6a5. Please try it and let us know. (Many of these will also land in
Firebug 1.5.1)

Reported by johnjbarton@johnjbarton.com on 2010-02-17 01:21:10

fbugissues commented 9 years ago

Reported by sebastianzartner on 2012-06-05 14:13:37