Apache Hop version?
latest (Docker image: apache/hop-web:latest)
Java version?
Default Java version included in the official hop-web docker image
Operating system
Linux
What happened?
When running Apache Hop Web behind a reverse proxy (like an OpenShift Route), the legacy /hop/status page fails to load static assets properly.
The action icons (such as run.svg, stop.svg, view.svg) are missing, and the action links are completely unclickable.
Upon inspecting the browser console (F12) and network tab, there are multiple 404 Not Found errors for the static files. The paths seem to be hardcoded or improperly resolving to /content/common-ui/... which fails to load when the application is served behind a reverse proxy.
Steps to reproduce the behavior
- Deploy
apache/hop-web:latest on a Kubernetes/OpenShift cluster.
- Expose the service via a reverse proxy / Ingress / Route.
- Open the Hop Web UI in the browser.
- Navigate to the Hop Server status page (e.g.,
https://<your-domain>/hop/status).
- Notice that action icons are missing and links cannot be clicked.
- Open browser DevTools (Console/Network tab) and observe
404 Not Found errors for /content/common-ui/... assets.
Expected behavior
The static assets and icons on the /hop/status page should load correctly using relative paths that are compatible with reverse proxies, and the links should be clickable.
Issue Priority
Priority: 3
Issue Component
Component: Hop Web, Component: Hop Server
Apache Hop version?
latest (Docker image: apache/hop-web:latest)
Java version?
Default Java version included in the official hop-web docker image
Operating system
Linux
What happened?
When running Apache Hop Web behind a reverse proxy (like an OpenShift Route), the legacy
/hop/statuspage fails to load static assets properly.The action icons (such as
run.svg,stop.svg,view.svg) are missing, and the action links are completely unclickable.Upon inspecting the browser console (F12) and network tab, there are multiple
404 Not Founderrors for the static files. The paths seem to be hardcoded or improperly resolving to/content/common-ui/...which fails to load when the application is served behind a reverse proxy.Steps to reproduce the behavior
apache/hop-web:lateston a Kubernetes/OpenShift cluster.https://<your-domain>/hop/status).404 Not Founderrors for/content/common-ui/...assets.Expected behavior
The static assets and icons on the
/hop/statuspage should load correctly using relative paths that are compatible with reverse proxies, and the links should be clickable.Issue Priority
Priority: 3
Issue Component
Component: Hop Web, Component: Hop Server