Hi!
Please(!) update ChangeLog when commiting new changes.
There is a whole lotta new errors in the test suite
in the form of:
Result was:
200 {} {1
x
0
}
Result should have been (exact matching):
200 1 x
tclresp-4.2 FAILED
Now, what IS this? I cannot remember seeing those
erro
i am suspecting this happened after encoding patches
Zoran Vasiljevic wrote:
Hi!
Please(!) update ChangeLog when commiting new changes.
There is a whole lotta new errors in the test suite
in the form of:
Result was:
200 {} {1
x
0
}
Result should have been (exact matching):
200 1 x
On 13.08.2006, at 17:21, Vlad Seryakov wrote:
i am suspecting this happened after encoding patches
WHAT encoding patches??? I see nothing in the ChangeLog!
Zoran
I remember my last chnage in keepalive but i am sure i ran make test at
that time, it was month ago, after that not sure about other changes
really, not many last time
Zoran Vasiljevic wrote:
On 13.08.2006, at 17:21, Vlad Seryakov wrote:
i am suspecting this happened after encoding patche
On 13.08.2006, at 17:28, Vlad Seryakov wrote:
I remember my last chnage in keepalive but i am sure i ran make
test at
that time, it was month ago, after that not sure about other changes
really, not many last time
Your last change was:
2006-07-21 Vlad Seryakov <[EMAIL PROTECTED]>
On Sun, Aug 13, 2006 at 05:36:33PM +0200, Zoran Vasiljevic wrote:
> That means: somebody did change the code (or the testsuite)
> w/o updating the ChangeLog file. I think I will have to go
> to the mail list archive and check the commit maillist as I
> did not get any emails about what was changed
On 13.08.2006, at 18:04, Andrew Piskorski wrote:
Using it shows that between 7/21 and 8/13, there was only one commit
to Naviserver (ignoring its various modules) by anyone other than
"vasiljevic", this one:
2006-08-08 12:07 eide
Ah, Bernd!
* tests/: encoding.test, tclresp.test
i think i found it, it is the change about switching into chunked mode
if encoding is used, thus returning the result with length prepended, so
all test are broken now.
when i disabled it in the sources, some tests are fine now, http.test,
but still others are broken
Zoran Vasiljevic wrote:
On 13.08.2006, at 17:55, Vlad Seryakov wrote:
i think i found it, it is the change about switching into chunked mode
if encoding is used, thus returning the result with length
prepended, so
all test are broken now.
when i disabled it in the sources, some tests are fine now, http.test,
but s
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 preven
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 sub
I do not want to remove anything if this breaks anybody's code.
This chunked-transfer-encoding thing is only a workaround until the
Content-Length bug is fixed.
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 so
Michael Lex schrieb:
It's only going to hit you if you use some other encoding than utf-8
and then only if you use a HTTP-client, that does not understand
chunked encoding. But every web-browser and virtually every other
client-software should understand this (It's a MUST part of the rfc).
..
13 matches
Mail list logo
