Re: utf-8 encoded htaccess?

"Martin Strand" <do.not.eat.yellow.snow@xxxxxxxxx> · Mon, 10 Sep 2007 12:52:24 +0200

On Mon, 10 Sep 2007 04:40:44 +0200, Vincent Bray <noodlet@xxxxxxxxx> wrote:

On 10/09/2007, Martin Strand <do.not.eat.yellow.snow@xxxxxxxxx> wrote:

This must be a UA problem - none of IE/FF/Opera decodes the name, they
must've forgotten to read rfc2617. :)

Or quite possibly an apache problem, given that this string must be
shoehorned in to the WWW-Authenticate header along with the other
tokens. Does the header look reasonable? I'm not sure if apache
supports this at all.

I did some experimenting with PHP. This script outputs an RFC compliant  

header (as far as i can tell) but IE/FF/Opera won't decode the realm name:

<?php

header("WWW-Authenticate: Basic realm=\"=?utf-8?B?5pel5pys6aaZ5aCC?=\"",  

true, 401);

?>

The same thing works fine for a filename so there's nothing wrong with the  

actual encoding:

<?php

header("Content-Disposition: attachment;  

filename=\"=?utf-8?B?5pel5pys6aaZ5aCC?=\"");

?>

It really seems to be a UA problem. According to those RFCs, both 'realm'  

and 'filename' are supposed to be 'quoted-string' and should be treated  

exactly the same. It just seems so weird that three major browser vendors  

would miss this.

Frustrating... :\

Martin

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx