httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10446] New: - spaces in link to http server seen as foreign characters in 1.3.26
Date Wed, 03 Jul 2002 15:32:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10446>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10446

spaces in link to http server seen as foreign characters in 1.3.26

           Summary: spaces in link to http server seen as foreign characters
                    in 1.3.26
           Product: Apache httpd-1.3
           Version: HEAD
          Platform: PC
               URL: http://www.profilehost.com/
        OS/Version: Linux
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: apache@tb2.com


Note: I'm unsure what the "HEAD" version is. Hopefully it means 1.3.26. :)

Hi, I run a free AOL Instant Messenger profile service called ProfileHost. So 
far, I have nearly 5,000 users. My web host recently upgraded Apache to 1.3.26 
and in this release, spaces from a link from within AOL Instant Messenger give 
a 400 error... But worked fine in previous versions of the Apache server. I 
tested it via a php script that uses apache_lookup_uri() and "THE_REQUEST" 
variable. The link I'm using from within AOL Instant Messenger is:

<html><a href="http://www.profilehost.com/view.php?user=taber&a=i&n=%n&"

target="_self">Click here to see my profile</a></html>

The %n variable is an AOL IM variable that gets swapped with the current person 
viewing the profile's screenname. Screennames with spaces in them cause the 400 
error. So far I have found no workaround for this. Apache seems to be catching 
the error before mod_rewrite has access to the URI... because it is seen as 
invalid now. If you  have any idea how I could possibly use .htaccess or 
somehow ignore this 400 error, I would very much appreciate the assistance.

Or, if you could please consider changing this back to how it was in previous 
releases, allowing plain spaces in the URI, that would be great! I figured I 
had no chance in hell of asking AOL to properly URL encode their outgoing links 
(converting spaces to %20), so I'm asking you for help instead. :) I also 
figured you would listen to me because we both are offering a free 
service/product! :)

Thank you very much for your time!
-Taber Buhl

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message