[Webkit-unassigned] [Bug 185473] New: Fetch: content-length header is being added to the safe-list

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=185473

            Bug ID: 185473
           Summary: Fetch: content-length header is being added to the
                    safe-list
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: shacharz at gmail.com

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

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180509/70ea1ed8/attachment.html>