A questions for the knowledgable SSL people here: I experimented with setting socket timeouts to 1 second during HTTP/2's keepalive reading and closing the connection after n such TIMEUP returns. That works nicely on cleartext connections, but https:// return APR_EOF on reads after the first APR_ETIMEUP. Am I seeing ghosts or is that something in SSL that regards timed-out reads as basically broken?
Thanks. -Stefan
