-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SttpClientInterpreter
does not propagate headers in the http response for websockets
#3959
Comments
I'm having some problems trying to reproduce the issue. See my attempt here: https://github.com/softwaremill/tapir/pull/3965/files Initially I was using However, with |
Could you perhaps take a stab at https://github.com/kamilkloch/tapir-correlation-id? |
Maybe in September. Ideally I'd need a minimized test case, or a really minimized app :) |
Would you like me to minimize it more? Deal? ;) |
Well if you could minimize it - of course, please do - though both me & @kciesielski are unavailable in August, sorry :) |
That is great to hear, very well deservered unplugged time for both of you. Will try to minimize. |
We are using tapir interceptor to enrich server responses with some contextual information (e.g. correlation id):
On the client side, we wrap tapir interpreter to extract correlation id from the response header and lift the original
to
In case of rest calls the wrapped tapir client properly extracts correlation id from the response.
In case of websockets, correlation id header is missing - the underlying
SttpClientInterpreter
returns a response without the header. A low-level sttp websocket client does receive the correlation id:Repo with the code: https://github.com/kamilkloch/tapir-correlation-id
The text was updated successfully, but these errors were encountered: