Re: HTTP::Request::Common : Specify POST fields separators ?

If that server expects that, it's not really looking for HTTP form data. You'll have to construct a body manually.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Comment on Re: HTTP::Request::Common : Specify POST fields separators ?

Replies are listed 'Best First'.
Re^2: HTTP::Request::Common : Specify POST fields separators ? by odrevet (Acolyte) on Jan 04, 2010 at 14:26 UTC
I understand, but the separator is still & and not \r\n	[reply]
Re^3: HTTP::Request::Common : Specify POST fields separators ? by afoken (Chancellor) on Jan 05, 2010 at 14:09 UTC
So, generate your own request body, as you were told. What you want is not HTTP, even if it nearly looks the same and you will probably be able to abuse HTTP tools to generate your custom request. You could start by generating a standard HTTP request, storing that into a variable, replace all "&" inside the body with newlines, and then sending that modified request over the wire. The very first reply looks like a good start point. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]