You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I investigated an issue, where websocket upgrades were failing. We have a service handling websockets living behind the vertx-http-proxy. This service is living on a different root path, than the vertx-http-proxy is exposing. Hence a path prefix is removed in the vertx-http-proxy with the help of a ProxyInterceptor. This works for normal http requests.
Version
4.3.8
Context
I investigated an issue, where websocket upgrades were failing. We have a service handling websockets living behind the
vertx-http-proxy
. This service is living on a different root path, than thevertx-http-proxy
is exposing. Hence a path prefix is removed in thevertx-http-proxy
with the help of aProxyInterceptor
. This works for normal http requests.However, it turns out the
ProxyInterceptor
s are not applied for websocket upgrades as websocket upgrades are handled and returned before the interceptors are applied.This behaviour results in the path prefix not being removed and the service running behind the proxy returning a 404 for the websocket upgrade.
The text was updated successfully, but these errors were encountered: