-
-
Notifications
You must be signed in to change notification settings - Fork 448
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
Body always empty? #223
Comments
It looks like we don't attempt to extract the body in HttpInterface. In my understanding: one issue with Would love anyone else's thoughts on this. I'll see what else I can come up with. |
Correct, we already have a listener to cache the body stream for logging purposes, maybe there is some way via Raven Java API to set such body so I can have it on my exceptions? |
Since you have the data available from your listener you should be able to make it work. Sadly it seems like it might be kind of annoying, We attach the I think you'd need your own I wonder what a more general solution could be... |
To be clear, I'd love your input here. I wonder if many users keep a cached copy of the body around because it can only be read once. Maybe some easy way for those users to hand off the body to us...? It'd be great to solve this for everyone, even those without the cached body. I don't know what we can do given the interface though. |
Did you have any luck with this @gionn ? |
Yeah, I've ended up using slf4j MDC facility to set some context tags, one of them contains the body of the request that generated an exception. |
Hi,
it looks like that in our setup raven is not capturing any http body in the context of the logged exception, while other things like cookies, headers and environment variables are there.
Any suggestions on how to debug this issue?
The text was updated successfully, but these errors were encountered: