post upgrade, relative URL support broken

[msambol]

Hi Dan,

I just upgraded to v4 from 3 and ran into a problem. In order to avoid opening a port in my router specifically for SIP, I had been running it at 

https://mydomain.com/sip/

I have one machine which listens on 443 and proxies to others depending on the URL, e.g. in this case to a PI running SIP for all URLs that start with /sip/

With version 3, this worked fine, but it doesn't work in 4. The first problem I tracked down is that base.html has

Code:

    <script src="/static/scripts/jquery-3.4.1.min.js"></script>
    <script src="/static/bootstrap-3.3.7/js/bootstrap.min.js"></script>
    <script src="/static/bootstrap-timepicker/js/bootstrap-timepicker.js"></script>

where previously it only had 

Code:

<link rel="stylesheet" href="$app_path('/static/...

I patched those manually, so now the main page shows up, but all the menu buttons are absolute URLs as well, e.g. the Options button goes to /vo

I could try tracking those links down, but it seems this is deeper than just changes to the HTML. Chrome dev tools reports:

jquery-3.4.1.min.js:2 GET https://mydomain.com/api/log?date=2020-06-09 net::ERR_BLOCKED_BY_CLIENT
jquery-3.4.1.min.js:2 GET https://mydomain.com/api/status 404 (Not Found)


Is there a way I can get the new version to work under /sip/? 

In the meantime I'll try changing my setup to use sip.mydomain.com instead.

---

Also, seemingly unrelated, while accessing it via local IP address rather than domain/sip I see a persistent error in chome developer tools:

jquery-3.4.1.min.js:2 GET http://10.0.0.128/api/log?date=2020-06-09 net::ERR_BLOCKED_BY_CLIENT

it looks like this fires and fails every 30 seconds.