Description
When I try to configure reverse proxy handler on location '/cluster' then I get 400 Bad request HTTP error. When I looked via Wireshark I can see that Undertow reverse-proxy handler create request like this GET HTTP/1.1 - path is missing. Although when I configure reverse proxy handler on different location, everything is working just fine.
Try with following:
/subsystem=undertow/server=my-new-server:add() /subsystem=undertow/server=my-new-server/host=my-new-host:add(alias=[localhost]) reload /subsystem=undertow/server=my-new-server/host=my-new-host/location=\/:add(handler=welcome-content) /socket-binding-group=standard-sockets/socket-binding=my-new-http:add(port=8787) /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=proxy-binding:add(host=localhost,port=8787) /subsystem=undertow/server=my-new-server/http-listener=my-listener:add(socket-binding=my-new-http) /subsystem=undertow/configuration=handler/reverse-proxy=myproxy:add() /subsystem=undertow/configuration=handler/reverse-proxy=myproxy/host=localhost:add(outbound-socket-binding=proxy-binding) /subsystem=undertow/server=default-server/host=default-host/location=\/proxy:add(handler=myproxy) /subsystem=undertow/server=default-server/host=default-host/location=\/cluster:add(handler=myproxy)
and then access:
localhost:8080/proxy <--- ok localhost:8080/cluster <--- fail
NOTE: when I try the same approach with EAP 7.0.0, both locations work just fine.
Attachments
Issue Links
- is blocked by
-
UNDERTOW-859 ProxyHandler fails with status 400 in some cases
-
- Resolved
-
- is incorporated by
-
JBEAP-6556 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha12
-
- Verified
-
-
-
- Verified
-