The INSTALL file in 1.0 now documents the need to set $FullUrl when running on a non-standard port. (I did not want to change the current behavior without a lot of testing.) --CliffordAdams
I believe that I have found a bug in the usemod code.

The bug concerns the page loaded after a page edit has been saved. This seems to affect the wiki when running on all non-standard ports.

After editing a page and clicking "save" the button, the refreshed page doesn't have the port number within the URL, and so the connection is refused. One of my users has sent me this log from his web proxy:

Using -relative sets $FullUrl to the simpler wiki.cgi, forcing the browser to regenerate the full URL. Seems to work for me, though can't say how universal the fix is. Unsure whether the fault lies in our assumptions of CGI.pm's url() function, or in CGI.pm itself. Presumably, one could also use -absolute with much the same effect.

I considered this as a fix, but I am also not sure how universal it is. (One thing to consider is that CGI.pm has changed significantly over the past few years, and I want to support almost any Perl 5 installation.) --CliffordAdams

I have had the problem but have no remedy as yet. The page does not refresh but the text does have the correct link in. Seems it might be a combination of perl and code but funny things do seem to happen on unusual port numbers.

One thing to try in this case is changing the $RedirType setting from 1 to 2. If that doesn't work, setting $RedirType to 3 will at least give you a page with a link to the right destination. --CliffordAdams