Issue 453078 in chromium: "Failed to load response data"

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Cr-Platform-DevTools Pri-2 Via-Wizard Type-Bug OS-Linux

New issue 453078 by matteosi...@gmail.com: "Failed to load response data"
https://code.google.com/p/chromium/issues/detail?id=453078

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/39.0.2171.99 Safari/537.36

Steps to reproduce the problem:
This is not systematically reproducible, but at times it happens:

1. Use the Developer Tools, Network tab
2. click on a request
3. click the "Response" tab

What is the expected behavior?
Should ALWAYS show the response data.
There doesn't exist any case in which it can be justified that the response
data cannot be shown

What went wrong?
The contents of the response are not shown: it says "Failed to load
response data".

The request was done succesfully, the response was obtained; the data was
loaded and actually used by the script that did the request, so there's no
possible reason for not being able to load response data, period.

This "Failed load response data" message shouldn't exist under any
circumstances. When a request is not succesful and no response is received
(which may be the case when a timeout occurs, cannot even think of another
case) you may see the "No response available" message or something like
that, but that's a different story.

Did this work before? N/A

Chrome version: 39.0.2171.99 Channel: n/a
OS Version: ubuntu 14.04
Flash Version: Shockwave Flash 16.0 r0

Attachments:
Screenshot from 2015-01-28 22:28:40.png 87.9 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: eus...@chromium.org

Comment #1 on issue 453078 by eus...@chromium.org: "Failed to load response
data"
https://code.google.com/p/chromium/issues/detail?id=453078

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: Duplicate
Mergedinto: 141129

Comment #2 on issue 453078 by eus...@chromium.org: "Failed to load response
data"
https://code.google.com/p/chromium/issues/detail?id=453078

As I see - you use "Preserve log" option. To avoid performance overhead
requests from previous page load are not captured.

[chro...@googlecode.com]

Comment #3 on issue 453078 by aa...@aaronblankenship.com: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

I use preserve log to actually preserve the log. If that option is checked
every piece of information should be accessible.

[chro...@googlecode.com]

Comment #5 on issue 453078 by zoot...@gmail.com: "Failed to load response
data"
https://code.google.com/p/chromium/issues/detail?id=453078

I preserve log because I don't want the log to be cleared on navigation.
I'm trying to debug a JSON problem. Clearing the response data from a
logged result and displaying "Failed to load response data" is clearly
wrong!

[chro...@googlecode.com]

Comment #6 on issue 453078 by verus360...@gmail.com: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

This is clearly a defect. If I enable the 'preserve log' option, the log
should be retained exactly as if the page navigation event had not occurred.

If performance is a concern, introduce a separate 'Preserve responses'
checkbox so that users can make the decision.

[chro...@googlecode.com]

Comment #7 on issue 453078 by p...@algumacoisa.org: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

I had to use Firefox to be able to debug a similar situation.
In my scenario, is login form which redirects to a error 500 page
with 'document.location', if that redirect happens after more than 1s the
response body is preserved..

[chro...@googlecode.com]

Comment #8 on issue 453078 by LiJu...@gmail.com: "Failed to load response
data"
https://code.google.com/p/chromium/issues/detail?id=453078

THIS IS ABSOLUTELY A BUG!

Please preserve ALL the request logs and information if enable "preserve
log" options, otherwise such a feature is useless.

[chro...@googlecode.com]

Comment #11 on issue 453078 by sergey.c...@gmail.com: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

Clearly this is bug. Fixing this would save developers many hours of
debugging.

[chro...@googlecode.com]

Comment #15 on issue 453078 by richch...@gmail.com: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

Took me awhile just to figure out what the problem was. Preserve log must
preserve the responses (without question), too. Thought it used to. Please
fix ASAP

[chro...@googlecode.com]

Updates:
Owner: ---
Labels: -Via-Wizard -OS-Linux

Comment #16 on issue 453078 by eus...@chromium.org: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #17 on issue 453078 by bradyvid...@gmail.com: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

definitely a bug - it's not expected behavior

[chro...@googlecode.com]

Comment #18 on issue 453078 by maxiwh...@gmail.com: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

Same thing here, very annoying bug, response should be kept even if the
page goes away.

[chro...@googlecode.com]

Comment #19 on issue 453078 by stm.swit...@gmail.com: "Failed to load
response data"
https://code.google.com/p/chromium/issues/detail?id=453078

Any news on this bug?