On Sunday 04:05 PM 8/2/2009, Torben Brosten wrote:
ns_httpspost depends on server's content-length header to be somewhat
accurate or greater than 0 if supplied.
That's true, though I'm not sure if it's a problem in the general case or
if it's ok based on the HTTP specs. It's definitely not
Looking through modules/https.tcl ..
ns_httpsopen depends on server's content-length header to be somewhat
accurate or greater than 0 if supplied.
iirc, AOLserver has a bug that returns inaccurate content-lengths,
sometimes 0.
Could this be a/the cause?
Torben
John Caruso wrote:
On
Torben Brosten wrote:
Looking through modules/https.tcl ..
ns_httpsopen
er, I mean.. ns_httpspost
depends on server's content-length header to be somewhat
accurate or greater than 0 if supplied.
In particular, won't this code break if a server's header returns
Content-length of 0?
On Tuesday 09:01 PM 7/21/2009, Mark Aufflick wrote:
You say that This bug ONLY occurs with an AOLserver client (any
version) running against an AOLserver 4 / nsopenssl 3.0beta26 server
- so you're saying this issue doesn't occur when using httpsget
against, say, Apache?
Yes, that's correct.
Hi John,
You say that This bug ONLY occurs with an AOLserver client (any
version) running against an AOLserver 4 / nsopenssl 3.0beta26 server
- so you're saying this issue doesn't occur when using httpsget
against, say, Apache?
It seems very odd that it would be server specific - that would fall
We've run into a bug with AOLserver 4.5.1 / nsopenssl 3.0beta26. The bug is
fully documented here:
https://sourceforge.net/tracker/?func=detailaid=2822117group_id=3152atid=103152
But the short version is that when using the nsopenssl client-side routines
(e.g. ns_httpsget), the result may
On Wednesday 03:17 PM 7/15/2009, Scott Goodwin wrote:
Tell me what version of OpenSSL you're running.
OpenSSL 0.9.8k. It's been happening for many years with different OpenSSL
versions as well.
- John
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply
John,
Tell me what version of OpenSSL you're running.
thanks,
/s.
On Jul 15, 2009, at 5:26 PM, John Caruso wrote:
We've run into a bug with AOLserver 4.5.1 / nsopenssl 3.0beta26.
The bug is fully documented here:
Your SF bug report says that you put in a 300 millisecond delay.
Where? Even if you think that such a fix is not good, it would be
helpful to at least know what works. It might help track down the bug,
or help others start looking at something smaller than
ns_httpsget/post.
You also talk about
On Wednesday 04:26 PM 7/15/2009, Tom Jackson wrote:
Your SF bug report says that you put in a 300 millisecond delay.
Where? Even if you think that such a fix is not good, it would be
helpful to at least know what works.
There's a massive amount of debugging I've done on this that's not
10 matches
Mail list logo
