On 13.08.2006, at 19:38, Michael Lex wrote:

As I see from the CVS, there were no changes to the C-code there?
Did you have to change the C-code??
I guess, Bernd will have to explain what he ment to do with that...

Bernd is on holiday right now. But i think i can explain the problem.
Bernd submitted a patch (or better workaround) to prevent Naviserver
from sending wrong content-length-headers. He simply made naviserver
send all data, that had to be converted to a different encoding, in
chunked transfer-encoding. Unfortunately nstest_http doesn't
understand chunked content. This patch was comitted on July, 13th.
When I worked on the encoding-tests, I had to add an OutputCharset
configuration parameter. So now Naviserver has to convert the content
and sends it in chunked mode, which nstest_http doesn't understand.
And the tests fail. If you remove this workaround, some of my new
encoding-tests still fail because of a wrong content-length. But this
is really a bug.

Michael,

I do not want to remove anything if this breaks anybody's code.
I just want to understand what is going on and how is this
going to hit me (or not) if I start to use this code?
Do I have to know somethind special? We do not set any special
encodings: we always serve utf8. Should I care?

Cheers,
Zoran



Michael

---------------------------------------------------------------------- --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel? cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel


Reply via email to