Welcome to the "trac"-ing site of http-access2!
[soap4r] [httpclient] [openpgp4u] [pkcs1] [logger] [csv] [vtr]

Ticket #217 (closed task: fixed)

Opened 10 months ago

Last modified 9 months ago

avoid Content-Length: 0 in request

Reported by: nahi Assigned to: nahi
Priority: high Milestone: 2.1.5
Component: core Version: 2.0
Keywords: Cc:

Change History

05/14/09 19:40:49 changed by nahi

If I understand correctly, Content-Length: 0 is required for KeepAlive?. Five HTTPClient tests fail without sending Content-Length: 0.

Maybe I miss another problem (I’m using httpclient to connect to BigIP for my job). Can you send me a wiredump? Thanks!

FYI: You can configure persistent connection by HTTPClient#protocol_version = ‘HTTP/1.0′.

05/25/09 17:57:03 changed by nahi

  • status changed from new to closed.
  • resolution set to fixed.

(In [279]) * do not send 'Content-Length: 0' when a request doesn't have message body. Some server application (EasySoap?++/0.6 for example) corrupts with the request with Content-Length: 0. cf. http://daemons.net/~clay/2009/05/03/ruby-why-do-you-torment-me/ . closes #217.

05/26/09 08:18:51 changed by nahi

  • status changed from closed to reopened.
  • resolution deleted.

need to check again. see comments of the blog.

05/26/09 14:01:20 changed by nahi

Thank you for valuable comment.

I almost full agree with you and I applied it along the line in r279. If I understand correctly. Content-Length header for request (HTTP::Message::Headers#set_request_header) is controlled based on @body_size (nil for no message body) after r279. Am I still misunderstand something?

Talking about ‘GET + message body’, HTTPClient doesn’t offer first class support. We need to use HTTPClient#request instead of HTTPClient#get. I don’t know it’s possible or not.

06/05/09 16:38:21 changed by nahi

  • status changed from reopened to closed.
  • resolution set to fixed.