Steps to reproduce the problem: 1. create a CORS fetch request to a url that has content-length in its response and doesn't add content-length to access-control-expose-headers 2. content-length should be accessible in the response's headers What is the expected behavior? When doing a CORS fetch request if content-length exists in the http response it should be exposed on the response headers even if it's not added to the access-control-expose-headers. What went wrong? content-length is not exposed see: https://github.com/whatwg/fetch/pull/626 https://github.com/w3c/web-platform-tests/pull/10930
Created attachment 346783 [details] Patch
Comment on attachment 346783 [details] Patch Attachment 346783 [details] did not pass mac-ews (mac): Output: https://webkit-queues.webkit.org/results/8801197 New failing tests: imported/w3c/web-platform-tests/fetch/api/cors/cors-filtering-worker.html
Created attachment 346786 [details] Archive of layout-test-results from ews102 for mac-sierra The attached test failures were seen while running run-webkit-tests on the mac-ews. Bot: ews102 Port: mac-sierra Platform: Mac OS X 10.12.6
Comment on attachment 346783 [details] Patch Attachment 346783 [details] did not pass mac-wk2-ews (mac-wk2): Output: https://webkit-queues.webkit.org/results/8801206 New failing tests: imported/w3c/web-platform-tests/fetch/api/cors/cors-filtering-worker.html
Created attachment 346787 [details] Archive of layout-test-results from ews104 for mac-sierra-wk2 The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews. Bot: ews104 Port: mac-sierra-wk2 Platform: Mac OS X 10.12.6
Created attachment 346788 [details] Patch
Comment on attachment 346788 [details] Patch Clearing flags on attachment: 346788 Committed r234840: <https://trac.webkit.org/changeset/234840>
All reviewed patches have been landed. Closing bug.
<rdar://problem/43274948>
Tested on Safari 12.01 and it's not exposed by default. When is it going to land ?
Hi, (In reply to shacharz from comment #10) > Tested on Safari 12.01 and it's not exposed by default. When is it going to > land ? Assuming you use OS X, a recent Safari Technology Preview should have this fix.