>Number:         2966
>Category:       mod_jserv
>Synopsis:       Escape characters not handled properly at initArgs
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Sep  7 05:40:00 PDT 1998
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.1, jserv 1.0beta
>Environment:
FreeBSD 2.2.6, JDK1.1.6, JSDK 2.0, JServ 1.0beta latest snap
>Description:
This patch will hopefully fix the remaining problem with the handling of 
escape (\) characters at initArgs.
>How-To-Repeat:
This problem arises when you have an initArgs string with a "\" not located 
at the end of the line.
>Fix:
Apply this patch to JServServletManager.java:

*** JServServletManager.java    Mon Sep  7 14:24:45 1998
--- JServServletManager.java.patched    Mon Sep  7 14:24:54 1998
***************
*** 650,662 ****
                                value.setLength(0);
                                state = NAME;
                                break;
-                       case '\\':
-                               if (++i < argsline.length()) {
-                                       c = argsline.charAt(i);
-                               } else {
-                                       // Trailing \ ignore.
-                                       continue;
-                               }
                        // Append the next character
                        default:
                                if (state == NAME) {
--- 650,655 ----
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]



Reply via email to