Skip to content
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

http-proxy example 400 response #188

Open
cherishs001 opened this issue Nov 8, 2019 · 5 comments
Open

http-proxy example 400 response #188

cherishs001 opened this issue Nov 8, 2019 · 5 comments
Labels
bug Something isn't working

Comments

@cherishs001
Copy link

having some trouble with the http-proxy example. It seems ClientRequest.send_stream results in a 400 response for any request that actually has a request body. It never even seems to hit the thing being proxied to. Not sure if I'm missing something or if the example is broken.

@svenstaro
Copy link
Contributor

Probably fixed by #186. Could you check?

@cosminci
Copy link

Does #186 mean actix can't do stream proxying? This sounds like a dealbreaker for use cases where large request payloads are received (i.e. > 10MB).

@vmalloc
Copy link
Contributor

vmalloc commented Nov 22, 2019

I didn’t follow up on the details in #186 but my guess is that this limitation is only relevant to Actix’s web client. I use actix to stream large request bodies to Amazon S3 without reading them all into memory. You will, however, need to do some more boilerplate setup given the current limitations of send and sync on errors and such

@svenstaro
Copy link
Contributor

svenstaro commented Nov 22, 2019 via email

@GopherJ
Copy link

GopherJ commented Mar 25, 2020

Any idea or any help on correct streaming?

EDIT: while testing, it seems actix-web's streaming method works well so I think the problem is just on awc

@robjtede robjtede added the bug Something isn't working label Mar 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants