-
Notifications
You must be signed in to change notification settings - Fork 657
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
HttpClient: proxy host and path become the request destination #490
Comments
Unfortunately this didn't fix it for me, with the latest |
@ttiurani Can you post here your logs? Also can you execute it with Hoverfly and with some other proxy server? Please enable the wire logging and
|
@violetagg here are two logs, that should show how things go wrong, the code is from a real example, so I masked the values a bit. Note the 0.7.9.RELEASE:
and 0.8.3.BUILD-20181101.191149-7:
|
@ttiurani Try with the latest snapshot, it should be OK. |
@violetagg nice, I confirmed that the fix works, thanks a lot! Are you planning a 0.8.3 release soon? Would be great if this fix would end up in the Spring releases sooner than later. |
Expected behavior
Using a TCP proxy doesn't change the destination of the request itself, but only proxies the request.
Actual behavior
With 0.7.9. this worked with the hoverfly proxy:
and the Destination was "http://www.example.org" but with 0.8.2 and this kind of refactoring:
The Destination becomes hoverfly itself, i.e. "localhost:1234". So setting the tcpClient.proxy overrides whatever I put into the uri of the call itself.
Steps to reproduce
Unfortunately didn't have time to create a short test case for this.
Reactor Netty version
0.8.2
JVM version (e.g.
java -version
)openjdk version "11" 2018-09-25
OpenJDK Runtime Environment AdoptOpenJDK (build 11+28)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11+28, mixed mode)
OS version (e.g.
uname -a
)OSX 10.13.6
The text was updated successfully, but these errors were encountered: