Zoran Vasiljevic schrieb:
> On 08.08.2006, at 11:48, Michael Lex wrote:
>
>> When no OutpuCharset is defined, naviserver will send the content
>> without transformation, that means utf-8. But according to the RFC
>> 2616 (HTTP 1.1) all content without an explicit "charset: ..." in the
>> Content-Type-Header should be treated as iso-8859-1 by the clients.
>> This causes problems when you have an incomplete configuration (w/o
>> OutputCharset).
>>
>
> Heh... should we simply add the UTF8 charset declaration
> in absence of the output encoding? I believe this would
> be the simplest "fix"?
>
at least for the tests, when no OutputCharset other than UTF-8 is specified.
...and none of its derivations, such as diacritical enconding on macs. i
would
think that the added charset declaration on a mac must be different.
recoding
utf-8 can affect the number of bytes as well.
-gustaf
PS: yes, the added signature is strange.
|
