From: merch-redmine@... Date: 2019-07-15T17:06:18+00:00 Subject: [ruby-core:93792] [Ruby master Feature#5764] Net::HTTP should assume HTTP/0.9 on unexpected responses Issue #5764 has been updated by jeremyevans0 (Jeremy Evans). ruby -v deleted (ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-darwin11.1.0] ) Assignee set to naruse (Yui NARUSE) Status changed from Open to Assigned Project changed from Ruby 1.8 to Ruby master Tracker changed from Bug to Feature This appears to still be the case in master, but I think this is a feature request for a "laxed" option. I'm not sure if we want to support such an option though. ---------------------------------------- Feature #5764: Net::HTTP should assume HTTP/0.9 on unexpected responses https://bugs.ruby-lang.org/issues/5764#change-79560 * Author: mstyer (Mike Styer) * Status: Assigned * Priority: Normal * Assignee: naruse (Yui NARUSE) * Target version: ---------------------------------------- Currently Net::HTTP.read_status_line throws Net::HTTPBadResponse if the status line does not conform to HTTP/1.1 specifications. But in cases when the web server implements a request size limit, it may not read HTTP/1.1 trailer after the request URI and may send back an HTTP/0.9 response. Nginx does this for 414 Request-URI Too Large responses: http://lxr.evanmiller.org/http/source/http/ngx_http_header_filter_module.c#L95 http://forum.nginx.org/read.php?2,52862,52862 Perl's Net::HTTP provides a "laxed" option to read_response_headers() to assume HTTP/0.9 if it can't find an HTTP/1.1 status line. Ruby should provide a similar option. -- https://bugs.ruby-lang.org/ Unsubscribe: