When you say that you cannot do "server" things, do you mean that you cannot touch your CMS or that you do not have root access to your HTTP server?
Because if you have access to your HTTP server, you can configure a very simple reverse proxy (with mod_proxy if you use Apache). This will allow you to use relative paths in your HTML, while the HTTP server will act as a proxy in any remote location. In fact, this method can also be used to mitigate some problems with cross-site scripting.
The main configuration directive to configure reverse proxies in mod_proxy is ProxyPass. Usually you use it as follows:
ProxyPass /css/ http://example.com/css_dir/
In this case, the browser will request https://yyy.example.com/css/main.css , but the server will serve this, acting as a proxy for http://example.com/css_dir/main.css . It will not trigger a browser warning and works great with SSL.
Daniel Vassallo
source share