Received: (qmail 54245 invoked by uid 501); 26 Sep 2000 12:13:37 -0000 Message-Id: <20000926121337.54243.qmail@locus.apache.org> Date: 26 Sep 2000 12:13:37 -0000 From: Massimo Santini Reply-To: santini@dsi.unimi.it To: submit@bugz.apache.org Subject: mod_rewrite escaping prevents the use of w3c recomanded cgi field separator ';' X-Send-Pr-Version: 3.110 >Number: 6586 >Category: mod_rewrite >Synopsis: mod_rewrite escaping prevents the use of w3c recomanded cgi field separator ';' >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Quarter: >Keywords: >Date-Required: >Class: duplicate >Submitter-Id: apache >Arrival-Date: Tue Sep 26 05:20:03 PDT 2000 >Closed-Date: >Last-Modified: >Originator: santini@dsi.unimi.it >Release: Apache/1.3.12 (Unix) >Organization: apache >Environment: Linux zorn 2.2.16-3 #1 Mon Jun 19 19:11:44 EDT 2000 i686 unknown gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Apache/1.3.12 (Unix) >Description: As noted in bug PR number 5633, mod_rewrite escapes QUERY_STRINGS on redirects. The use of ';' as a cgi field separator (as recomanded by w3c) becomes impossible since after rewrinting it becomes '%3b'. It should be addressed at least with explicit options.L >How-To-Repeat: RewriteRule ^/R/([A-Za-z_]+)$ /R.php?A=1 [R,L] >Fix: User side: step back to '&' (which is not escaped), but not recomanded. Developer side: add an option to control escaping. >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]