Re: BOM

Am 27.06.2007 um 17:26 schrieb Andreas Prilop:

>
> On Wed, 27 Jun 2007, Douglas Perreault wrote:
>
>> In the meantime, here is a sample file exhibiting the problem:
>> http://dev.inbliss.info/UTF1.css
>
> | Content-Type: text/css;charset=ISO-8859-1
> | Server: Microsoft-IIS/6.0
> | MicrosoftOfficeWebServer: 5.0_Pub
> | X-Powered-By: ASP.NET
>
> Your server sends clearly
>
>    charset=ISO-8859-1
>
> The problem is with your broken Microsoft server.

I confirm that.

Maybe the document
.NET Framework General Reference
globalization Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/en-us/library/hy4kkhe0.aspx

helps you to configure your webserver correctly.


Concerning your desire to individually configure the encoding instead  
of rely on the default encoding, the following section of http:// 
msdn2.microsoft.com/en-us/library/hy4kkhe0.aspx may be of interest  
for you:

<cite>
responseEncoding

Optional attribute.

Specifies the content encoding of responses.

The default encoding is UTF-8, which is specified in the  
globalization section in the Machine.config file that was created  
when the .NET Framework was installed. If response encoding is not  
specified in a Machine.config or Web.config file, encoding defaults  
to the Regional Options locale setting for the computer.

In single-server applications, this attribute and the  
responseEncoding attribute should be the same. For the less common  
case (multiple-server applications where the default server encodings  
are different), you can vary the request and response encoding by  
using local Web.config files.
</cite>

It seems, that IIS/ASP.Net gives you the ability to use individual  
Web.config files to overwrite the default response encoding.


> Perhaps you should look at
>  http://httpd.apache.org/

Full ACK.



Hope, this helps.

Sierk
-- 
Sierk Bornemann
email:            sierkb@gmx.de
WWW:              http://sierkbornemann.de/

Received on Wednesday, 27 June 2007 15:58:06 UTC