On Sat, Dec 10, 2016 at 9:25 PM, Rasool, Kaja Mohideen (Nokia - IN)
wrote:
> Ok, maybe, TCP is doing it. Is there any other API using which I can specify
> the payload length & number of bytes for padding to send a TLS Heartbeat
> request? Then, I can use that API
disable O_NAGLE on the socket?
-Kyle H
On Sat, Dec 10, 2016 at 8:04 AM, Salz, Rich wrote:
> Heartbeats? Yuk, why.
>
>
>
> Most likely, TCP is buffering things until you get a big enough data
> packet. I don’t know how to address that.
>
> --
> openssl-users mailing list
>
Ok, maybe, TCP is doing it. Is there any other API using which I can specify
the payload length & number of bytes for padding to send a TLS Heartbeat
request? Then, I can use that API to send out a big enough heartbeat request so
my server recognize & responds to it.
// Kaja
From:
Heartbeats? Yuk, why.
Most likely, TCP is buffering things until you get a big enough data packet.
I don’t know how to address that.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi,
I'm trying to develop a server (Java - Netty NIO Library + OpenSSL) / client (C
+ OpenSSL) applications.
A. I started off writing my server using Netty+OpenSSL and used some python
scripts available in web (https://gist.github.com/takeshixx/10107280) to test
whether TLS Heartbeat with