Bug 161381 - [Fetch API] Blob not found URL should result in a network error
Summary: [Fetch API] Blob not found URL should result in a network error
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: youenn fablet
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-30 08:10 PDT by youenn fablet
Modified: 2016-08-30 11:24 PDT (History)
1 user (show)

See Also:

Attachments
Patch (7.81 KB, patch)
2016-08-30 08:14 PDT, youenn fablet 		no flags Details | Formatted Diff | Diff
Fixing FileReaderLoader error generation (21.86 KB, patch)
2016-08-30 09:36 PDT, youenn fablet 		no flags Details | Formatted Diff | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description youenn fablet 2016-08-30 08:10:53 PDT 
As per https://fetch.spec.whatwg.org/#basic-fetch, if blob is null (not found e.g.), a network error should be generated.
Currently we generate a 404 error response.
Comment 1 youenn fablet 2016-08-30 08:14:18 PDT 
Created attachment 287393 [details]
Patch
Comment 2 youenn fablet 2016-08-30 09:36:34 PDT 
Created attachment 287401 [details]
Fixing FileReaderLoader error generation
Comment 3 WebKit Commit Bot 2016-08-30 11:24:15 PDT 
Comment on attachment 287401 [details]
Fixing FileReaderLoader error generation

Clearing flags on attachment: 287401

Committed r205190: <http://trac.webkit.org/changeset/205190>
Comment 4 WebKit Commit Bot 2016-08-30 11:24:25 PDT 
All reviewed patches have been landed.  Closing bug.