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
Using RoundTripper results in the request body being consumed, which means that the request retrieved with session.Request() in the OnResponse handler is without a body. I understand that this is how RoundTripper works in Go.
Would it be reasonable to set the consumed body back to the request within gomitmproxy at this point?
I need the request body within the OnResponse handler, and currently, I'm passing it through session.SetProphere. This approach seems wrong, as I would expect the request body to be available in the OnResponse handler. However, I may be missing a reason why your code doesn't set the request body back to the request.
If you find it reasonable to add the body back to the request after RoundTripper consumes it, I'm ready to prepare a PR.
The text was updated successfully, but these errors were encountered:
Using RoundTripper results in the request body being consumed, which means that the request retrieved with
session.Request()
in the OnResponse handler is without a body. I understand that this is how RoundTripper works in Go.Would it be reasonable to set the consumed body back to the request within gomitmproxy at this point?
I need the request body within the OnResponse handler, and currently, I'm passing it through
session.SetProp
here. This approach seems wrong, as I would expect the request body to be available in the OnResponse handler. However, I may be missing a reason why your code doesn't set the request body back to the request.If you find it reasonable to add the body back to the request after RoundTripper consumes it, I'm ready to prepare a PR.
The text was updated successfully, but these errors were encountered: