OT: anyone else find the signature strange? ;)
On 8/14/06, Michael Lex [EMAIL PROTECTED] wrote:
Perhaps, it is even better to include a default OutputCharset (utf-8),
when reading the configuration. I think the right place would be
NsUpdateEncodings, but i can be wrong ;-)
Michael
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
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
