New issue
Advanced search Search tips

Issue 625519 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 625532



Sign in to add a comment

Assertion failed when fetch() from in-scope document got a redirect response to other origin

Project Member Reported by shimazu@chromium.org, Jul 4 2016

Issue description

The following is printed when fetch() is called from in-scope document and the response is redirect which needs CORS preflight.

==

ASSERTION FAILED: m_fallbackRequestForServiceWorker.isNull()
../../third_party/WebKit/Source/core/loader/DocumentThreadableLoader.cpp(770) : void blink::DocumentThreadableLoader::handleSuccessfulFinish(unsigned long, double)

==

This happens because, after getting redirect response, DocumentThreadableLoader::redirectReceived will send CORS preflight as usual without unsetting m_fallbackRequestForServiceWorker, though m_fallbackRequestForServiceWorker is set for SW request at the beginning.


 
I'll upload a CL to add tests for this problem.
Blocking: 625532
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 4 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)
Still available. we need to revisit Issue 625532 again.
 Issue 797170  has been merged into this issue.

Comment 6 by shimazu@google.com, Jan 10 2018

Issue 625532 has been merged into this issue.
Project Member

Comment 7 by sheriffbot@chromium.org, Jan 10

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: -horo@chromium.org toyoshim@chromium.org shimazu@chromium.org yhirano@chromium.org
Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
I'm wondering if OOB-CORS may change something, though I'm not familiar with it. What do you think?

Sign in to add a comment