Are web sockets exposed to the stack of middleware? #614
-
I assume not. I assume a web socket is an opaque tunnel as far as Axum's middleware is concerned (other than the initial request to upgrade). Is that correct? My use case is enforcing authentication on each "request", whereas a web socket message isn't a "request". |
Beta Was this translation helpful? Give feedback.
Answered by
davidpdrsn
Dec 11, 2021
Replies: 1 comment 1 reply
-
Correct. The client makes a regular HTTP request that is upgraded to a websocket connection at which point middleware are no longer involved. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
davidpdrsn
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Correct.
The client makes a regular HTTP request that is upgraded to a websocket connection at which point middleware are no longer involved.