-
Notifications
You must be signed in to change notification settings - Fork 66
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
Cannot get proxy to work with Tesla adapter #148
Comments
I've got the same issue. |
Looking into the code, there's no handling for |
According to elixir-tesla/tesla#271 and the Stream section of the documentation, streaming responses isn't supported. But the current behaviour isn't ideal - we should fail much earlier than that if we can detect this. I'll see what can be done here. |
It now throws an Point taken about the configuration; I'd like to make a pass at the |
Released in v2.4.0 |
Hello,
I am trying out this plug, and ran into a strange issue. Configuring tesla_client option was also kind of tricky, and I don't know if I have it setup correctly. The problem I see is that when configured with Tesla (using either mint or hackney as tesla_client), the requests just hang and never complete. Using hackney directly instead of tesla seems to work.
Here's how I have it setup:
mix.exs:
endpoint.ex:
When I make a request to http://localhost:4000/test/test.json, I see this in the logs:
15:21:59.484 [info] GET /test/test.json
and the browser keeps loading and loading with no response.
Any clues what I did wrong above? I was unable to figure out how to pass tesla_client option in config.exs, so I ended up passing the options in the forward call.
Any help would be appreciated.....thanks for your time!
The text was updated successfully, but these errors were encountered: