On Tue, 15 Aug 2023 at 18:11, Donald Russell wrote:
> Using the hole/elastic/fanin trick worked.
>
> We’ll, that’s hitting the code with the ugly stick isn’t it? Lol.
>
> I’m hoping that’s a “bug?” related to linger not lingering properly.
>
> Seriously, thanks for the workaround.
>
> Cheers,
>
Using the hole/elastic/fanin trick worked.
We’ll, that’s hitting the code with the ugly stick isn’t it? Lol.
I’m hoping that’s a “bug?” related to linger not lingering properly.
Seriously, thanks for the workaround.
Cheers,
Don
On Tue, Aug 15, 2023 at 02:44 Rob van der Heij wrote:
> I
On Tue, 15 Aug 2023 at 14:17, Alan Altmark wrote:
> That’s not just SSL. Only the app knows when it has received all the data.
> Only then should it close the socket. So an app waits for a certain
> amount of time or until it gets and end-of-data indicator. That might be a
> specific byte
That’s not just SSL. Only the app knows when it has received all the data. Only
then should it close the socket. So an app waits for a certain amount of time
or until it gets and end-of-data indicator. That might be a specific byte
sequence or it might be a closed connection (eg ftp).
There
I suspect this is a feature of the VM SSL implementation to close the
inbound socket when the application closes the outbound connection,
discarding any data that is in transit outside or in the SSL path. That
happened initially also in the other direction, but I was able to change
some minds
