From: "meta (mathew murphy)" <meta@...>
Date: 2012-11-30T05:02:32+09:00
Subject: [ruby-core:50340] [ruby-trunk - Bug #7469][Open] WEBrick "Could not determine content-length of response body. Set content-length of the response..." even when content-length is set


Issue #7469 has been reported by meta (mathew murphy).

----------------------------------------
Bug #7469: WEBrick "Could not determine content-length of response body. Set content-length of the response..." even when content-length is set
https://bugs.ruby-lang.org/issues/7469

Author: meta (mathew murphy)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]


Minimal demonstration code:

########
require 'webrick'

class BugDemonstrator < WEBrick::HTTPServlet::AbstractServlet
  def do_GET(request, response)
    response.body = ''
    response.status = 204
    response.content_length = 0
  end
end

server = WEBrick::HTTPServer.new(:Port => 8080, :AccessLog => [])
server.mount "/", BugDemonstrator
trap("INT") do
  server.shutdown
end
server.start
########

Output when run, connecting to localhost:8080 to issue an HTTP GET:

$ ruby webrickbug.rb                                        
[2012-11-29 13:21:25] INFO  WEBrick 1.3.1                                       
[2012-11-29 13:21:25] INFO  ruby 1.9.3 (2012-11-10) [x86_64-linux]              
[2012-11-29 13:21:25] WARN  TCPServer Error: Address already in use - bind(2)   
[2012-11-29 13:21:25] INFO  WEBrick::HTTPServer#start: pid=4941 port=8080       
[2012-11-29 13:21:29] WARN  Could not determine content-length of response body. Set content-length of the response or set Response#chunked = true              
^C[2012-11-29 13:21:32] INFO  going to shutdown ...                             
[2012-11-29 13:21:32] INFO  WEBrick::HTTPServer#start done.
$ ruby --version
ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]
$

I'm doing literally what the warning message says to do -- i.e. setting the content-length of the response -- but I'm still getting the warning.


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