From: lengarvey@...
Date: 2014-06-27T16:32:54+00:00
Subject: [ruby-core:63372] [ruby-trunk - Bug #9986] [Open] WEBrick content-length being set when transfer-encoding is chunked

Issue #9986 has been reported by Leonard Garvey.

----------------------------------------
Bug #9986: WEBrick content-length being set when transfer-encoding is chunked
https://bugs.ruby-lang.org/issues/9986

* Author: Leonard Garvey
* Status: Open
* Priority: Normal
* Assignee: Hiroshi Nakamura
* Category: lib
* Target version: 
* ruby -v: trunk, ruby 2.1.2p95
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
It's possible to get WEBrick to return both Transfer-Encoding: chunked and a calculated Content-length header. If the Transfer-encoding header is set via WEBrick::HTTPResponse#[]= then #chunked? will return false and the content length will be set during the setup_headers method. This causes issues with rack and safari (example code for rack can be seen https://github.com/rack/rack/issues/618#issuecomment-47355492). As far as I'm aware WEBrick shouldn't return a content-length when a transfer-encoding chunked header is present. Messages MUST NOT include both a Content-Length header field and a transfer-coding. as per http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html

The following test can be placed into test_httpresponse.rb to demonstrate the issue:

~~~
    def test_200_chunked_does_not_set_content_length
      res.body        = 'hello'
      res.status      = 200
      res.chunked     = false
      res["Transfer-Encoding"] = 'chunked'
      res.setup_header

      assert_nil res.header.fetch('content-length', nil)
    end
~~~

I've added a patchfile which includes the above test and a fix for the issue.



---Files--------------------------------
webrick_transfer_encoding_chunked_content_length.patch (1.07 KB)


-- 
https://bugs.ruby-lang.org/