WUI links to pages using configured port #2299

New Issue

tahoe-lafs · 2014-09-17T03:54:52Z

dsoprea commented

2014-09-17 03:54:52 +00:00

I'm forwarding :3456 to my local machine as :34561 via SSH, but whenever I click a link/button, like "View File or Directory" or "Recent and Active Operations", I get redirected to a page at :3456 and hit a 404. In the case of the "Recent and Active Operations" link, the anchor-tag just specifies "status" for the href and I don't think it's being preempted in JS (the next JS that runs seems to be something like "unloadEvent"). Therefore, it might be getting redirected at the web-server or the backend.

I'm forwarding :3456 to my local machine as :34561 via SSH, but whenever I click a link/button, like "View File or Directory" or "Recent and Active Operations", I get redirected to a page at :3456 and hit a 404. In the case of the "Recent and Active Operations" link, the anchor-tag just specifies "status" for the *href* and I don't think it's being preempted in JS (the next JS that runs seems to be something like "unloadEvent"). Therefore, it might be getting redirected at the web-server or the backend.

tahoe-lafs added the

labels 2014-09-17 03:54:52 +00:00

tahoe-lafs added this to the undecided milestone 2014-09-17 03:54:52 +00:00

warner commented

2014-09-19 21:50:05 +00:00

Updating component (the "website" component is actually for https://tahoe-lafs.org, but "code-frontend-web" is for the WUI).

Hrm, I thought we'd fixed all of the href targets and form/button targets to use relative URLs. Originally there were lots of absolute URLs (which caused exactly this problem: we had some AllMyData servers that basically reverse-proxied requests into a localhost:3456 URL, and every once in a while the internal host+port would leak). I remember that some of the absolute URLs were not easy to fix (but I don't remember the reaons right now).

Nothing should be getting updated with JS.. it should all be the responsiblity of the HTML-generating code in src/allmydata/web/directory.py .

Updating component (the "website" component is actually for <https://tahoe-lafs.org>, but "code-frontend-web" is for the WUI). Hrm, I thought we'd fixed all of the href targets and form/button targets to use relative URLs. Originally there were lots of absolute URLs (which caused exactly this problem: we had some [AllMyData](wiki/AllMyData) servers that basically reverse-proxied requests into a localhost:3456 URL, and every once in a while the internal host+port would leak). I remember that some of the absolute URLs were not easy to fix (but I don't remember the reaons right now). Nothing should be getting updated with JS.. it should all be the responsiblity of the HTML-generating code in src/allmydata/web/directory.py .