Re: How to avoid URL-Encoding in LWP POST Request

Otherwise the web application will not understand the request.
That web application is broken(using broken HTTP/CGI library).

Can anyone tell me how I can deactivate automatic URL encoding in variable names?
Since LWP exist to do the encoding, the simplest way is not to use LWP.

Comment on Re: How to avoid URL-Encoding in LWP POST Request

Replies are listed 'Best First'.
Re^2: How to avoid URL-Encoding in LWP POST Request by Your Mother (Archbishop) on Nov 24, 2008 at 17:21 UTC
Someone will correct me if I'm wrong, I hope, but I think this is not correct. I believe the requirement to encode brackets and parens and a few other chars is relatively new (added to the specs in 2005 if I searched right) and therefore there is going to be code in the wild that still uses the old behavior which makes it no more broken than HTML v XHTML. Confusing and problematic, but not broken. ++ to almut below for showing how to handle it in this case.	[reply]
Re^3: How to avoid URL-Encoding in LWP POST Request by Anonymous Monk on Nov 25, 2008 at 01:53 UTC
RFC 1738 Uniform Resource Locators (URL) December 1994	[reply]
Re^4: How to avoid URL-Encoding in LWP POST Request by Your Mother (Archbishop) on Nov 25, 2008 at 06:44 UTC
As the terms "POST," "CGI," and "application/x-www-form-urlencoded" do not appear in that spec, I would prefer to see a different link to reconsider; though I am open to the possibility I'm wrong and I'd like to know if it's the case. :)	[reply]
Re^5: How to avoid URL-Encoding in LWP POST Request by Anonymous Monk on Nov 25, 2008 at 07:41 UTC