[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-bugdb
Subject:    general/5918: SCRIPT_NAME value varies depending on UC letter
From:       Henry Sobotka <sobotka () axess ! com>
Date:       2000-03-23 2:48:29
[Download RAW message or body]


>Number:         5918
>Category:       general
>Synopsis:       SCRIPT_NAME value varies depending on UC letter
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Mar 22 18:50:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     sobotka@axess.com
>Release:        1.3.12
>Organization:
apache
>Environment:
OS/2 4.5 (WSeB), running binaries from Apache website
>Description:
For example, the URL
http://prospero.aleph1010/cgi-bin/printenv/emx/include/stdlib.h
produces SCRIPT_NAME="/cgi-bin/printenv". Changing it to:
http://prospero.aleph1010/cgi-bin/printenv/eMx/include/stdlib.h produces
SCRIPT_NAME="/cgi-bin/printenv/eMx", 
http://prospero.aleph1010/cgi-bin/printenv/emx/incluDe/stdlib.h produces
SCRIPT_NAME="/cgi-bin/printenv/emx/incluDe" and
http://prospero.aleph1010/cgi-bin/printenv/emx/include/stdLib.h produces
SCRIPT_NAME="/cgi-bin/printenv/emx/include/stdLib.h"

As you can see, the value of SCRIPT_NAME stretches to the last path component
containing an uppercase letter.

This may be related, but I've also noticed that PATH_INFO consistently gets
squished to lowercase. Although the OS/2 filesystem is case-insensitive,
this creates problems with programs that expect an exact match.




>How-To-Repeat:
It may well be an OS/2-specific problem. The above examples are derived from
the cgi-bin/printenv included with the distribution.
>Fix:
No, but I'll be looking at the code to try to track it down.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> 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!     ]
 
 

[prev in list] [next in list] [prev in thread] [next in thread]