What I just realized is ICS has no demo for HTTP SSL POST. Any untested code
is buggy!
I will try to modify the POST demo for SSL.
Regards,
SZ
On Sat, Dec 25, 2010 at 4:16 PM, Arno Garrels wrote:
> If you provide a simple test case including both client and server
> applications with source,
Arno
You are correct - Microsoft Windows Server 2008 R2 is 64-Bit Only
You could get Microsoft Windows Server 2008 in 32-Bit or 64-Bit.
Mark Moss
- Original Message -
From:
To:
Sent: Saturday, December 25, 2010 5:00 AM
Subject: TWSocket Digest, Vol 404, Issue 6
Joyeux Noël et Bonne Année 2011 à tous !
De Montréal, Québec, Canada
On Thu, Dec 23, 2010 at 7:26 PM, DZ-Jay wrote:
> ¡Feliz Navidad y un próspero Año Nuevo a todos!
>
> (Merry Christmas and a prosperous New Year to everyone!)
>
> dZ.
>
>
> On Dec 23, 2010, at 17:40, Maurizio Lotauro wrot
If you provide a simple test case including both client and server
applications with source, preferable in Delphi, that reproduces the
problem I'll download and install server 2008 trial and take a look
at it.
--
Arno Garrels
Fastream Technologies wrote:
> Dear Arno,
>
> It does work on Win7
Dear Arno,
It does work on Win7 but does NOT work on Win2008 and Win2008R2. It works
perfectly with NO SSL on all Windows. The HTTP client does not raise any
exception--just 10053 and StatusCode=0 issues. I have uploaded the cert/pkey
at,
http://www.fastream.com/ics/certpkey.zip
It is a 4096-bit
Fastream Technologies wrote:
> Hello,
>
> With the HttpCli, I get 10053 when lots of consecutive POSTs are made
> with SSL. I first thought it is related to the 4096 bit self-signed
> cert we used but it does not happen on Win2008.
So it works on 2008?
> The test machine is
> remote (in the Neth
Hello Francois,
I already knew that but it also happens when the connection is between local
ICS SSL client and server. I have no idea how this could be prevented?
Also sometimes the client returns no 10053 but StatusCode = 0!
Regards,
SZ
On Sat, Dec 25, 2010 at 11:25 AM, Francois PIETTE wrot
Error 10053 is WSAECONNABORTED.
Software caused connection abort.
An established connection was aborted by the software in your host computer,
possibly due to a data transmission time-out or protocol error.
http://msdn.microsoft.com/en-us/library/ms740668(v=vs.85).aspx
--
francois.pie...@overby
Additional info: Here's the class which sometimes gives 10053 and sometimes
StatusCode = 0 when run against a server with self-signed SSL cert:
class WebClient
{
private:
TSslContext *sslContext;
AdminClient *adminClient;
bool aborted;
TMemoryStream *sendStream;
public:
TMemoryStream *receiveS
