Webpositive won't open links for localhost on port other than 80

[jprostko]

Hello,

I was using Fossil in Haiku, and noticed that its web interface via fossil ui no longer works in Web+. (Note that fossil ui automatically launches Web+ after it is entered in the terminal.)

I get the following error dialog box in Web+ after running fossil ui from the command line...

Error loading ​http://localhost:8080/doc/tip/www/index.wiki: Connection refused

If I run fossil ui --port 80, then it works perfectly. Any port other than 80 results in the "connection refused" error message. Qupzilla loads the URL just fine regardless of the port, so it only affects Web+. Also, using 127.0.0.1 instead of localhost does not at all remedy the problem, as I tried that as well to be thorough.

Steps to reproduce:

$ pkgman install fossil $ mkdir repos fossil $ cd repos $ fossil clone ​http://fossil-scm.org fossil.fsl $ cd ../fossil $ fossil open ../repos/fossil.fsl $ fossil ui

Please note this is a GCC2 hybrid build, hrev47571, running HaikuWebKit 1.4.1-3.

(The About window for Web+ needs updated, as it mentions HaikuWebKit 1.4.0 still.)

[pulkomandy]

I'm not sure how this is supposed to work. When requesting ​http://localhost:8080, Fossil sends a redirect to ​http://localhost/doc/tip/www/index.wiki (the port is gone). However, other browsers seems to get away with this.

Manually loading the page at ​http://localhost:8080/doc/tip/www/index.wiki exposes more problems, however, as all resources are referenced using relative URIs ("/path"), and this time it's WebKit failing to add the port to the requests. I will have a look. I noticed Fossil uses the <base/> html tag, this time with the proper port. So there's no reason WebKit gets things wrong here.

[pulkomandy]

Ok, found the problem (on our side obviously). Fixed in hrev47586. Thanks for reporting!

[jprostko]

Replying to pulkomandy:

Ok, found the problem (on our side obviously). Fixed in hrev47586. Thanks for reporting!

Thanks for the fix. I probably could have been more thorough by trying to host a web server on port 8080 as well to check its behavior, but I am glad this was enough information for you to be able to solve the problem.

Confirmed as fixed for me as well.