Hmm no, that's not really it... that's more so that you don't pass URLs starting with /app1/
onwards to the application, which would not be aware of that subpath.
I think I need something that intercepts the content being served to the client, and inserts /app1/
into all hardcoded absolute paths.
For example, let's say on app1's root I have an index.html that contains:
...
src="/static/image.jpg"
...
It should be dynamically served as:
...
src="/app1/static/image.jpg"
...
WEI is a proposed modification to Chrome/Chromium that doesn't even exist yet, and that would have the side effect of blocking adblockers on every site that implements WEI.
This here is an already existing change to the YouTube service that blocks adblockers on YouTube, across all browsers, Firefox included. It does not use or need WEI to do this.