New issue
Advanced search Search tips

Issue 718589 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
mmenke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

HTTP error pages for empty response don't appear when DevTools is open.

Project Member Reported by lgar...@chromium.org, May 4 2017 
Chrome 60.0.3088.3
OSX 10.12.4

What steps will reproduce the problem?
(1) Visit https://httpbin.org/status/404 (or, say, 403)
(2) Open DevTools and refresh.

What is the expected result?
The error page remains.

What happens instead?
The content viewport turns blank.

mmenke@, based on  Issue 632778  it seems you implemented this; could you triage?

Comment 1 by mmenke@chromium.org, May 4 2017

Cc: mmenke@chromium.org
Components: -Internals>Network>HTTP
Owner: ----
Status: Untriaged (was: Assigned)
I didn't, actually, just added text to the pre-existing page.  I'm not familiar with renderer-size navigation, loading, or devtools.  Seems like since devtools is breaking this, the devtools team would know best how devtools modifies page loading.  It may even be deliberate behavior.

Comment 2 Deleted

Comment 3 by mmenke@chromium.org, May 4 2017 

Actually, as I think about this, I'm pretty sure this is deliberate behavior.  If someone is debugging their own webpage, we display the returned page, instead of a generic error page.  If their server returns an HTTP error page with an empty body, that's a valid HTTP response, so we display it.  Loading the error page may even destroy devtools info related to the failed page load, with default settings.

Comment 4 by mmenke@chromium.org, May 4 2017 

And it's deliberate - see https://cs.chromium.org/chromium/src/content/renderer/render_frame_impl.cc?l=3995

I'll defer to the devtools team if this is what we want, but I assume so.
►

Sign in to add a comment