Problem:
Our Node.js proxy (using Express and http-proxy-middleware) correctly forwards requests but fails when handling relative resource URLs (images, CSS, and scripts).
For example, an image tag like <img src="/header.png"> gets requested as just: /header.png (incorrect) instead of: anothersite.com/header.png (correct).
This breaks styles and assets on proxied pages.
Steps to Reproduce
1. Set up the proxy with the code from repos latest and currently only existing version beta .6
2. Load a website with relative URLs through the proxy.
3. Observe broken images, styles, and scripts.
Proposed Solution
All relative URLs should be converted to absolute URLs from the target domain.
Example: <img src="/header.png"> → <img src="http://anothersite.com/header.png">
Problem:
Our Node.js proxy (using Express and http-proxy-middleware) correctly forwards requests but fails when handling relative resource URLs (images, CSS, and scripts).
For example, an image tag like
<img src="/header.png">gets requested as just:/header.png(incorrect) instead of:anothersite.com/header.png(correct).This breaks styles and assets on proxied pages.
Steps to Reproduce
1. Set up the proxy with the code from repos latest and currently only existing version beta .6
2. Load a website with relative URLs through the proxy.
3. Observe broken images, styles, and scripts.
Proposed Solution
All relative URLs should be converted to absolute URLs from the target domain.
Example:
<img src="/header.png">→<img src="http://anothersite.com/header.png">