Hi Everyone.
I see a couple of people having similar proxy issues but mine isn’t exactly the same.
So I had my platform working under Apache 2.4.52.
I run a reverse proxy setup with SSL termination handling requests for our VR portail (https://socialdream.fr).
I have the main application running on internal port 8080, and Apache configured to proxy_pass requests from 443 to 8080.
I had the ProxyPassReverse directive properly configured, so external URLs generated by the app would rewrite from :8080 back to standard https:// format.
However, I upgraded Apache to 2.4.57 this weekend following security patches, and now when our therapists try to generate shareable links for VR session reports, the URLs include the :8080 port and do NOT get rewritten to clean https:// format.
My reverse proxy config handles the 443 to 8080 transformation for incoming requests just fine…
Current Apache config:
ProxyPass /vr-portal/ http://localhost:8080/
ProxyPassReverse /vr-portal/ http://localhost:8080/
The internal app generates links like https://mydomain.com:8080/vr-portal/session/123 instead of the clean https://mydomain.com/vr-portal/session/123.
This is problematic because we share these links with healthcare professionals and patients, and the port number looks unprofessional and confuses users.
What gives? Anyone encountered similar URL rewriting issues after Apache updates?
Any fix suggestions would be greatly appreciated!