New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 474914 link

Starred by 1 user

Issue metadata

Status: Fixed
Closed: Apr 2015
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Sign in to add a comment

Ban cors responses for client requests.

Project Member Reported by, Apr 8 2015

Issue description

The Fetch spec has been changed.
> If one of the following conditions is true, return a network error:
>   response's type is "error".
>   request's mode is not "no-cors" and response's type is "opaque".
>   request is a client request and response's type is neither "basic" nor "default".

related issue on spec:
Labels: Cr-Blink-Fetch

Comment 2 by, Apr 15 2015

Labels: M-44
Status: Started
Project Member

Comment 3 by, Apr 15 2015

The following revision refers to this bug:

r193776 | | 2015-04-15T10:26:50.909227Z

Changed paths:

[ServiceWorker] Treat cors response as a network error for client requests.

The fetch spec has changed.
Spec issue:

BUG= 474914 

Review URL:

Comment 4 by, Apr 16 2015

Status: Fixed

Comment 5 by, Aug 5 2015

Labels: -Cr-Blink-Fetch Cr-Blink-FetchAPI

Comment 6 by, Nov 27 2015

Labels: -Cr-Blink-FetchAPI Cr-Blink-Network-FetchAPI

Sign in to add a comment