>> 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
while(t--);
printf("\n");
t=1000; while(t--);
---joke mode OFF--------
--
View this message in context:
http://www.nabble.com/Last-portion-SSL_read-only-after-a-SSL_write-.--Please-Help.-tp18717834p
> 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
RROR_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
>
>
&g
uot;\r\n", 2);
Thanks Peter
--
View this message in context:
http://www.nabble.com/Last-portion-SSL_read-only-after-a-SSL_write-.--Please-Help.-tp18717834p18767511.html
Sent from the OpenSSL - Dev mailing list archive at Nabble.com.
_
> > not send the second request until you have received the entire first
> > reply.
> yes you are right but the indication for "nothing else to read"
> is invalid.
Where are you getting this indication from? If your answer is anything other
than "my HTTP implementation", then you are confused. O
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
t-Type: text/xml; charset=UTF-8
Content-Length: 609
SOAPAction: "getActiveEventTypes"
empty line
609 bytes
Perhabs I have to add something like
"Allow SEND ALL DATA AT ONCE"
thank you
Peter
--
View this message in context:
http://www.nabble.com/Last-portion-SSL_read-only-after-a-SSL_
> 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
Ok,plz try this:
http://www.student.uni-oldenburg.de/rainer.valentin/test/
--
View this message in context:
http://www.nabble.com/Last-portion-SSL_read-only-after-a-SSL_write-.--Please-Help.-tp18717834p18731385.html
Sent from the OpenSSL - Dev mailing list archive at Nabble.com
wrote:
>
>
>
> ftp://erbse:[EMAIL PROTECTED]/
>
> Please copy this link above in your browser address line
> your browser will be able to follow this link
>
> --
> View this message in context:
> http://www.nabble.com/Last-portion-SSL_read-only-after-a-SSL_write-.
ftp://erbse:[EMAIL PROTECTED]/
Please copy this link above in your browser address line
your browser will be able to follow this link
--
View this message in context:
http://www.nabble.com/Last-portion-SSL_read-only-after-a-SSL_write-.--Please-Help.-tp18717834p18729136.html
Sent from
o more to read".
>
> But this obviously doesn't work. Perhabs doesnt work on w32 machines.
>
> You are right I have to make the next request when all is read.
> The question is, how can I detect the read has finished ?
>
>
> thanks Peter
>
>
>
>
>
>
> --
&
stion is, how can I detect the read has finished ?
thanks Peter
--
View this message in context:
http://www.nabble.com/Last-portion-SSL_read-only-after-a-SSL_write-.--Please-Help.-tp18717834p18725602.html
Sent from the OpenSSL - Dev
> 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
View this message in context:
http://www.nabble.com/Last-portion-SSL_read-only-after-a-SSL_write-.--Please-Help.-tp18717834p18717834.html
Sent from the OpenSSL - Dev mailing list archive at Nabble.com.
__
OpenS
17 matches
Mail list logo
