[Webkit-unassigned] [Bug 188586] New: [Cocoa] HEAD request should behave as same as GET request for Content-Length header.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Aug 14 16:07:08 PDT 2018


            Bug ID: 188586
           Summary: [Cocoa] HEAD request should behave as same as GET
                    request for Content-Length header.
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Platform
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: Basuke.Suzuki at sony.com

In the http/tests/xmlhttprequest/methods.html test, 

GET request doesn't send Content-Length field. The test log of 'GET(null bytes)' indicates no Content-Length header is sent.

> GET(""): GET(null bytes), Content-Type: null
> GET(null): GET(null bytes), Content-Type: null
> GET("123"): GET(null bytes), Content-Type: null

But http/tests/xmlhttprequest/methods-expected.txt, HEAD seems sending Content-Length header with value of 0.

> HEAD(""): HEAD(0 bytes), Content-Type: null
> HEAD(null): HEAD(0 bytes), Content-Type: null
> HEAD("123"): HEAD(0 bytes), Content-Type: null

As specification defined, HEAD should be as close identical as GET request.
"The HTTP HEAD method requests the headers that are returned if the specified resource would be requested with an HTTP GET method"

Soup and Curl returns (null bytes) which is same with GET requests.

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/20180814/fb922c45/attachment.html>

More information about the webkit-unassigned mailing list