forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CORS preflight should use the default max-age on parse failure
- When failing to parse "access-control-max-age", use the default value (5 seconds) in stead of 0. - Negative value is not a parse error. - Make the parser robust against integer overflow. Note the parsing logic is still underspecified. See whatwg/fetch#814. Bug: 651743 Change-Id: I4c2dcb3812cf757235c57298dfe17a7e4fe2e489 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2755991 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#863191}
- Loading branch information
1 parent
5d2b5a9
commit e9f67b8
Showing
3 changed files
with
24 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9 changes: 0 additions & 9 deletions
9
third_party/blink/web_tests/external/wpt/cors/preflight-cache-expected.txt
This file was deleted.
Oops, something went wrong.