My only idea to get around this would be to configure a list of parameter names in the template system where spaces can safely be reconverted to +-characters.Well, you're free to encode your data anyway you want (as long as the resulting URL is valid), but if you're not using "CGI encoding", you shouldn't have CGI::Util::unescape decode it. You should do one of these:
In reply to Re: CGI-class changes + to space for BASE64-data
by JavaFan
in thread CGI-class changes + to space for BASE64-data
by Pickwick
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |