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=12814>. 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=12814 login through URL [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-09-19 14:41 ------- Apache never sees stuff before the @ in the URL. Rather, the browser takes this stuff, BASE64 encodes it, and sends it in the Authorization HTTP request header. Therefore, the problem you are having is entirely with the browser, not the server. The server is only responsible for removing the BASE64 encoding, not for URL-decoding or any such thing. See RFC2617. In general, I wouldn't expect sending the userid/password in the URL to be a very reliable technique across browsers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
