DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34602>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34602 ------- Additional Comments From [EMAIL PROTECTED] 2007-10-22 01:48 ------- (In reply to comment #39) > I think mod_rewrite should not reencode unless I tell it to, or at the very > least, let me tell it not to. I quite agree. Those that say that it's correct should be campaigning for a documentation change saying "it's not possible to pass URL-unsafe parameters (i.e. those that require urlencoding) through mod_rewrite". I suspect that the vast majority of tutorials, documentation and articles about mod_rewrite are broken by this bug - the only reason they work as they are is pure luck and simplistic examples. > If a patch exists and has not been released then what kind of money are we > talking here to get it fixed in a major relase? I don't have a job but i'd > be > willing to put a few dollars towards getting this fixed. Me too. Without a patch the choices are : don't use apache, don't use mod_rewrite or (shiver) double encode everything. I have another workaround that's workable at the moment - instead of urlencoding params, I base64- encode them. Really ugly, but it works. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
