188586 2018-08-14 16:07:08 -0700 [Cocoa] HEAD request should behave as same as GET request for Content-Length header. 2020-05-18 00:02:18 -0700 1 1 1 Unclassified WebKit Platform WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 1 basuke basuke achristensen ap basuke rbuis webkit-bug-importer youennf oldest_to_newest 1450143 0 basuke 2018-08-14 16:07:08 -0700 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. https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD "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. 1653495 1 rbuis 2020-05-17 23:36:58 -0700 It would be nice to have HEAD behave as GET here, in order to pass more WPT tests and align with other platforms (like gtk). However this seems like CFNetwork behavior and maybe not necessarily a WebKit bug? 1653501 2 youennf 2020-05-18 00:02:08 -0700 <rdar://problem/56144949>