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
Right now server (struct Server) has a vector of hosts from where it would accept incoming requests
At the same time this setting could be all together ignored by users of the library, when they implement Server
But if users decide to use allowed_host functionality they may experience the following:
When one calls create_reply_authenticator on struct Server if uses server.secret, which I assume to be the same across all hosts, which may connect to the server
Not sure if that's always the case, but if not - then correct reply authenticator won't be created if host secret doesn't match server's secret
That would should be fixed at some point, if there is an ask
The text was updated successfully, but these errors were encountered:
Right now server (struct Server) has a vector of hosts from where it would accept incoming requests
At the same time this setting could be all together ignored by users of the library, when they implement Server
But if users decide to use allowed_host functionality they may experience the following:
When one calls create_reply_authenticator on struct Server if uses server.secret, which I assume to be the same across all hosts, which may connect to the server
Not sure if that's always the case, but if not - then correct reply authenticator won't be created if host secret doesn't match server's secret
That would should be fixed at some point, if there is an ask
The text was updated successfully, but these errors were encountered: