Summary: | Show HTTP status code in CORS messages logged to devtools console that can indirectly result from HTTP errors | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | sideshowbarker <mike> | ||||||||||||||||||||||||||||||||||||
Component: | Web Inspector | Assignee: | sideshowbarker <mike> | ||||||||||||||||||||||||||||||||||||
Status: | RESOLVED FIXED | ||||||||||||||||||||||||||||||||||||||
Severity: | Enhancement | CC: | achristensen, cdumez, darin, ehutchison, eric.carlson, ews-watchlist, glenn, inspector-bugzilla-changes, japhet, jer.noble, katherine_cheney, mkwst, philipj, sergio, webkit-bug-importer | ||||||||||||||||||||||||||||||||||||
Priority: | P2 | Keywords: | InRadar | ||||||||||||||||||||||||||||||||||||
Version: | WebKit Nightly Build | ||||||||||||||||||||||||||||||||||||||
Hardware: | Unspecified | ||||||||||||||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||||||||||||||
Attachments: |
|
Description
sideshowbarker
2021-10-18 18:08:06 PDT
I should have mentioned in the issue description that I’ve written Gecko and Blink patches for this: * https://bugzilla.mozilla.org/show_bug.cgi?id=1736026 is the Gecko bug. The patch for that should be landing in the trunk there this week. * https://bugs.chromium.org/p/chromium/issues/detail?id=1260776 is the Chromium bug. The patch there is going take a while longer to land. Created attachment 441669 [details]
Patch
Created attachment 441690 [details]
Patch
Created attachment 441691 [details]
Patch
Created attachment 441699 [details]
Patch
Created attachment 441703 [details]
Patch
Created attachment 441704 [details]
Patch
Created attachment 441710 [details]
Patch
Created attachment 441726 [details]
Patch
I’m looking at the test failures and I see this: https://ews-build.s3-us-west-2.amazonaws.com/Windows-EWS/r441710-110694/results.html …and that’s failing because there’s a difference between the expected output and the actual output: https://ews-build.s3-us-west-2.amazonaws.com/Windows-EWS/r441710-110694/http/tests/xmlhttprequest/access-control-preflight-not-successful-pretty-diff.html -CONSOLE MESSAGE: Preflight response is not successful +CONSOLE MESSAGE: Preflight response is not successful. Status code: 302 That is, specifically, the expected output has no `Status code: 302` while the actual output does. But the patch does actually include a change to the expected output at http/tests/xmlhttprequest/access-control-preflight-not-successful-expected.txt — see https://bugs.webkit.org/attachment.cgi?id=441726&action=diff#a/LayoutTests/http/tests/xmlhttprequest/access-control-preflight-not-successful-expected.txt_sec1 However, for some reason the expected output that the EWS test is picking up at https://ews-build.s3-us-west-2.amazonaws.com/Windows-EWS/r441710-110694/http/tests/xmlhttprequest/access-control-preflight-not-successful-expected.txt doesn’t include the change. So I don’t understand why the change from the patch isn’t reflected in the version the EWS test is using — and I don’t have an idea how to fix it… $ find LayoutTests -name access-control-preflight-not-successful-expected.txt LayoutTests/platform/win/http/tests/xmlhttprequest/access-control-preflight-not-successful-expected.txt LayoutTests/platform/mac-wk1/http/tests/xmlhttprequest/access-control-preflight-not-successful-expected.txt LayoutTests/http/tests/xmlhttprequest/access-control-preflight-not-successful-expected.txt There are different test expectations files for different platforms. You'll probably need to update all of them. Created attachment 442005 [details]
Patch
Created attachment 442009 [details]
Patch
Created attachment 442022 [details]
Patch
Created attachment 442076 [details]
Patch
Created attachment 442085 [details]
Patch
Created attachment 442097 [details]
Patch
Created attachment 442114 [details]
Patch
Created attachment 442125 [details]
Patch
(In reply to Alex Christensen from comment #11) > > There are different test expectations files for different platforms. You'll > probably need to update all of them. Aha, thanks — I’ve now updated all the tests, and EWS is all green. So I think this is ready for review from whoever might have time. Incidentally, the equivalent Firefox change has now landed and will ship in Firefox 95. - https://hg.mozilla.org/mozilla-central/rev/2b65a0fbcf8b - https://bugzilla.mozilla.org/show_bug.cgi?id=1736026 ChangeLog entry in Source/WebKit/ChangeLog contains OOPS!. Comment on attachment 442125 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=442125&action=review > Source/WebKit/ChangeLog:28 > + Reviewed by NOBODY (OOPS!). double NOBODY line. Created attachment 443028 [details]
Patch
Committed r285145 (243782@main): <https://commits.webkit.org/243782@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 443028 [details]. Patch broke a few tests on iOS EWS: http/tests/app-privacy-report/user-attribution-preflight-async.html http/tests/app-privacy-report/user-attribution-preflight-sync.html http/tests/app-privacy-report/app-attribution-preflight-async.html http/tests/app-privacy-report/app-attribution-preflight-sync.html http/tests/privateClickMeasurement/attribution-conversion-through-fetch-keepalive.html Re-opening for a patch. Fixed test expectations in http://trac.webkit.org/changeset/285166/webkit. (In reply to Eric Hutchison from comment #26) > Patch broke a few tests on iOS EWS: > > http/tests/app-privacy-report/user-attribution-preflight-async.html > http/tests/app-privacy-report/user-attribution-preflight-sync.html > http/tests/app-privacy-report/app-attribution-preflight-async.html > http/tests/app-privacy-report/app-attribution-preflight-sync.html > http/tests/privateClickMeasurement/attribution-conversion-through-fetch- > keepalive.html (In reply to Kate Cheney from comment #27) > Fixed test expectations in http://trac.webkit.org/changeset/285166/webkit. Thanks much — and sorry for having not been more thorough myself — to have identified those tests as needing changes. (In reply to Michael[tm] Smith from comment #28) > (In reply to Eric Hutchison from comment #26) > > Patch broke a few tests on iOS EWS: > > > > http/tests/app-privacy-report/user-attribution-preflight-async.html > > http/tests/app-privacy-report/user-attribution-preflight-sync.html > > http/tests/app-privacy-report/app-attribution-preflight-async.html > > http/tests/app-privacy-report/app-attribution-preflight-sync.html > > http/tests/privateClickMeasurement/attribution-conversion-through-fetch- > > keepalive.html > > (In reply to Kate Cheney from comment #27) > > Fixed test expectations in http://trac.webkit.org/changeset/285166/webkit. > > Thanks much — and sorry for having not been more thorough myself — to have > identified those tests as needing changes. No worries, those tests don't run on open source EWS bots for various reasons so it would have been very tricky to catch them the first time around! http/tests/privateClickMeasurement/attribution-conversion-through-fetch-keepalive.html continues to fail on iOS15 on EWS and Opensource. Creating new bug report for failing test: http/tests/privateClickMeasurement/attribution-conversion-through-fetch-keepalive.html Rebaselined http/tests/privateClickMeasurement/attribution-conversion-through-fetch-keepalive.html at https://trac.webkit.org/changeset/285218/webkit (In reply to Eric Hutchison from comment #31) > Creating new bug report for failing test: > http/tests/privateClickMeasurement/attribution-conversion-through-fetch- > keepalive.html Disregard, re-baselined instead. |