>> As I mentioned before, TCP is a stream protocol, not a message
>> protocol, so when you expect to receive all data before sending
>> another request over the same TCP socket, that is plain *wrong*,
>> though some people here appear to think this is possible.
>
> How would any interactive TCP pro
>Your code still has a fundamental and serious error. It tells the server
>that it is compliant with HTTP 1.1 when it is not.
yes, thats not clean solution.
I plan to take nanohttp.
There is a reference but unfortunately there is no manual.
I have to trial and error. :-(
Peter
---jo
> On Fri, 1 Aug 2008 08:26:55 +0200, Ger Hobbelt said:
>
> I'm glad this works for you, but be warned: the fact that that cute
> hack works in your environment now will not guarantee it will work
> elsewhere. The fact that you need to transmit another few ('faked')
> bytes to get the data you
> Hurrey
> I have the solution!
> :clap::-D
>
> If SSL_get_error give SSL_ERROR_NONE
> I test with strcmp ( at the end, "") .
> because all data from the server must end with "".
> If my data is not complete I send CR LF and the last 975 Bytes appeared
> SSL_write(mySSL->ssl,"\r\n", 2);
So
I'm glad this works for you, but be warned: the fact that that cute
hack works in your environment now will not guarantee it will work
elsewhere. The fact that you need to transmit another few ('faked')
bytes to get the data you want is a clear sign there's a TCP stream
(or SSL BIO) issue underlyin
Hurrey
I have the solution!
:clap::-D
If SSL_get_error give SSL_ERROR_NONE
I test with strcmp ( at the end, "") .
because all data from the server must end with "".
If my data is not complete I send CR LF and the last 975 Bytes appeared
SSL_write(mySSL->ssl,"\r\n", 2);
Thanks Peter
-
On Wed, Jul 30, 2008 at 07:32:26AM -0700, David Schwartz wrote:
>
> > Hallo
>
> Okay, you have two choices.
>
> 1) You can pipeline, where you send the next request before you receive the
> entire reply to the previous request. In this case, you may receive the rest
> of the reply to the first r
> Hallo
Okay, you have two choices.
1) You can pipeline, where you send the next request before you receive the
entire reply to the previous request. In this case, you may receive the rest
of the reply to the first request after you send the second.
2) You can not pipeline, where you don't send
Sounds to me like a case of a pending renegotiation or other alarm
signal happening and application level code not allowing this due to
your particular implementation of read/write loops, but that is a long
shot, as it may be due to several other issues as well.
To quickly get that Win32 item out
Thank you for the fast answer. :-)
On
ftp://erbse:[EMAIL PROTECTED]/
there is the request/response string and the function SSL_WR_RD().C
but SSL_read says "there is no more to read" stops the loop
because SSL_get_error give SSL_ERROR_NONE and return from function.
The request/response
> Hallo
>
> I made a simple SSL Client on win32
> The request and response works perfectly
> when the amount of data is small enough
>
> I made a request with SSL_write
> Servers answers with "..200 OK ..." etc
>
> SSL_read gives 7159 bytes.
> SSL_get_error gives allways SSL_ERROR_NONE
> and the
11 matches
Mail list logo
