Closed
Bug 675602
Opened 13 years ago
Closed 12 years ago
Web console show "Cannot show responses of type «(null)»" for 304 "Not modified" responses
Categories
(DevTools :: General, defect)
DevTools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: tonn81, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0
Build ID: 20110622232440
Steps to reproduce:
0. Opened Firefox
1. Opened web console
2. Enabled logging of requests/responses
3. Opened site that does 304 responses
4. Clicked on that request in web console
4. Scrolled down to the response content block
Actual results:
See "Cannot show responses of type «(null)»" in response content block
Expected results:
Response content block should show «(null)».
Also it would be great there one more field appear that would show actual value given to browser core (taken from cache).
Comment 1•13 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:8.0a1) Gecko/20110802 Firefox/8.0a1
Artem, can you please provide a link to a website that generates 304 responses?
Thanks!
Reporter | ||
Comment 2•13 years ago
|
||
Sample of the 304 page that produces the same bug is http://feeds.feedburner.com/~ff/couchdb?d=G79ilh31hkQ
Comment 3•13 years ago
|
||
Mozilla/5.0 (X11; Linux x86_64; rv:9.0a1) Gecko/20110822 Firefox/9.0a1
The actual result for me is: <<Unable to display responses of type "(null)">> in "unknown content type" tab.
Taking the last phrase from comment 0 into consideration, Artem, would this rather fit as an enhancement issue?
Reporter | ||
Comment 4•13 years ago
|
||
(In reply to Virgil Dicu from comment #3)
> Taking the last phrase from comment 0 into consideration, Artem, would this
> rather fit as an enhancement issue?
This is a bug as in the worst case it should show "(null)" instead of this "Unable to display" message. That might also lead to some mem leak or security hole. Please confirm it as you reproduced that.
As of my comment - there are two ways to show that response and I'm not sure what is more suitable:
* show response as is (i.e. "(null)")
* show actual content given to JS (i.e. the previous content)
It would be great if we show both.
Comment 5•13 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:9.0a1) Gecko/20110829 Firefox/9.0a1
Mozilla/5.0 (X11; Linux i686; rv:9.0a1) Gecko/20110818 Firefox/9.0a1
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0a1) Gecko/20110829 Firefox/9.0a1
Mozilla/5.0 (Windows NT 5.1; rv:9.0a1) Gecko/20110829 Firefox/9.0a1
Reproducible on Ubuntu 11.04, Windows XP and 7, Mac X OS 10.6 using the site provided in comment 2.
Steps:
1. Open Firefox
2. Open web console
3. Enable logging of requests/responses (right click web console)
3. Open site that does 304 responses (http://feeds.feedburner.com/~ff/couchdb?d=G79ilh31hkQ)
4. Reload the web page.
5. Click the last request.
Actual result: <<Unable to display responses of type "(null)">> under "unknown content type"
Expected results: Cached image
Last good nightly: 2011-01-11
First bad nightly: 2011-01-12
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4413ed6ba5a5&tochange=c0e05d518f57
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
Version: 5 Branch → Trunk
Comment 6•12 years ago
|
||
found this during triage. This appears to be fixed. Closing.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•