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
I'm having trouble loading nsopenssl with AOLserver 4.5.1. Despite
multiple attempts to address the problem, I'm going nowhere. Details
below. I'd greatly appreciate advice. --Prem Thomas
Details
===
64-bit x86
OpenSolaris (Nexenta: SunOS 5.11 kernel with a Ubuntu Hardy 8.04
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
