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 y
I'm new to Naviserver and I'm not quite sure about the intended use of ns_conn
encoding.
There are three situation where it is possible to change the encoding by hand:
1. When using ns_write, you can set the encoding with ns_startcontent
-type. You could also use ns_conn encoding, but ns_startco
Hi Stephen,
I asked my colleague Michael to apply your patch and start writing tests for
the encoding. He wrote some and it looks like there should some other things
be considered/fixed first to make them meaningful.
After that we can discuss a solution for the Content-Length/Encoding problem
