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.
In reply to Re^2: How to avoid URL-Encoding in LWP POST Request
by Your Mother
in thread How to avoid URL-Encoding in LWP POST Request
by Angeldust
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |