You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clients or bots not sending SNI hostname or an unknown one in message are a completely normal thing. This should not be an error. Instead the loglevel should raise only (Debug) on clients with no SNI field or hostname. So we can handle them better.
Imagine (Debug) Client sent empty or unknown SNI hostname, taking the fallback route
If an optional fallback server was defined on a custom IP:PORT by the user, we send all requests with empty or unknown SNI hostname there.
What do you think?
The text was updated successfully, but these errors were encountered:
This is similar to what we do in the HTTP parser, if no hostname is
there we can't do much but it's not really an error.
This was suggested in #6.
Signed-off-by: Antoine Tenart <[email protected]>
Great server! Very fast and stable for me. There is some improvement possible:
Clients or bots not sending SNI hostname or an unknown one in message are a completely normal thing. This should not be an error. Instead the loglevel should raise only (Debug) on clients with no SNI field or hostname. So we can handle them better.
Imagine
(Debug) Client sent empty or unknown SNI hostname, taking the fallback route
If an optional fallback server was defined on a custom IP:PORT by the user, we send all requests with empty or unknown SNI hostname there.
What do you think?
The text was updated successfully, but these errors were encountered: