Bug in QUIC example and/or docs
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
From SSL_handle_events docs:
SSL_handle_events() can be used only with the following types of SSL object:
- DTLS SSL objects
- QUIC connection SSL objects
But in quic/http3 example SSL_handle_events also called for listener SSL* object, see: https://github.com/openssl/openssl/blob/master/demos/http3/ossl-nghttp3-demo-server.c#L758
So who is wrong? Docs or demo?
Also, there is no example/demo/docs how to calculate SSL_get_event_timeout if we have a many QUIC connections.
When we have a single connection, we can use that connection's timeout in select/epoll. But what if we have multiple connections? What timeout should we specify in select/epoll?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the SSL_handle_events documentation with demos/http3/ossl-nghttp3-demo-server.c around line 758. Then inspect the SSL_get_event_timeout guidance for a single connection and the select/epoll questions. Done means resolving whether the listener call is valid and documenting or correcting the multi-connection timeout behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- documentation, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100