Soundness of using ConnectInfo for Per-Connection state #3090
Closed
2ndDerivative
started this conversation in
General
Replies: 1 comment
-
To add to this: It was sound in 0.7 but became impossible in 0.8 to cheat a bit and simply add the Connected impl as now there's a trait conflict. In my crate i give an example how you can approach per-connection tracking by adding a Listener wrapper and using that to implant a fresh per-connection state on every accept(). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello people!
I wanted to ask the more cracked of you if you're seeing any holes in my idea to use ConnectInfo for per-connection state like a Kerberos authentication state.
I implemented a middleware with it axum-negotiate-layer, which works so far (on Windows at least, sorry..), but wanted to ask if there might be any soundness holes in doing that. From what I saw the connect-info gets created once per connection, but I'm not 100% sure if that's guaranteed.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions