-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Using interceptors on multipart request #123
Comments
Any fix for this ? I am getting the same issue. |
Hi, I'm looking into it, however I do this on my spare time, which is definitely not enough. Pull requests are always welcomed though. 😄 |
At the moment, the way that you can work with Multipart Requests would be to do something like in the example project. In there, you'll find a way to do requests without necessarily needing to listen to the stream. I'm still looking for a way to "clone" the stream and data into a new one without having the stream either closed or listened to but it might take me a while to figure out a scalable solution. |
Its the same implementation on the example code that I used but it still has the same issue |
What I meant with the example is that you might not need to listen to the stream, or is there any specific reason that you |
When I don't listen to the stream the logged response is StreamedResponse object |
Yes, you could work with the |
At least if you don't depend on |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Any progress with fixing issue ? |
When i use a logging interceptor on a multipart request it returns StreamedResponse and if i listen to this object i get "Bad state exception stream has already been listened to"
The text was updated successfully, but these errors were encountered: