RESOLVED FIXED 169680
LayoutTests/imported/w3c/web-platform-tests/cors/preflight-failure.htm should use localhost/127.0.0.1 
https://bugs.webkit.org/show_bug.cgi?id=169680
Summary LayoutTests/imported/w3c/web-platform-tests/cors/preflight-failure.htm should...
youenn fablet
Reported 2017-03-15 09:20:55 PDT
LayoutTests/imported/w3c/web-platform-tests/cors/preflight-failure.htm should use localhost/127.0.0.1
Attachments
Patch (15.39 KB, patch)
2017-03-15 09:22 PDT, youenn fablet 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2017-03-15 09:22:58 PDT
Created attachment 304505 [details] Patch
Alexey Proskuryakov
Comment 2 2017-03-15 19:26:44 PDT
Comment on attachment 304505 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=304505&action=review > LayoutTests/imported/w3c/web-platform-tests/cors/preflight-failure-expected.txt:4 > +Harness Error (TIMEOUT), message = null Is this expected?
youenn fablet
Comment 3 2017-03-15 20:09:06 PDT
(In reply to comment #2) > Comment on attachment 304505 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=304505&action=review > > > LayoutTests/imported/w3c/web-platform-tests/cors/preflight-failure-expected.txt:4 > > +Harness Error (TIMEOUT), message = null > > Is this expected? I suspect that the web process is not notified for 1XX responses and end up timing out. We should fix that.
youenn fablet
Comment 4 2017-03-21 22:17:55 PDT
Submitted web-platform-tests pull request: https://github.com/w3c/web-platform-tests/pull/5193
youenn fablet
Comment 5 2017-10-14 16:46:04 PDT
Test was changed upstreamed and reimported
Note You need to log in before you can comment on or make changes to this bug.