Hallo Olaf, it's a session problem. Port 8080 does not help, but I cross checked on Archlinux, when I first click on the Login link, a session prefix is added to the internal links, and after login, that session prefix is everywhere in the html source. But on WSL2 that does not work somehow, I cleaned up the Wiki DB and started again, but same problem Regards, Thorsten
PS Before that, the links look the same: WSL2/Debian <div id="menuLogin"><a href="-2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login">Log in</a></div> Archlinux: <div id="menuLogin"><a href="-2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login">Log in</a></div> => click on login <div id="menuLogin"><a href="56462155004771490~-2.html?*Menu=+0&*Tab=+1&*ID=$login&*ID=$login">Log in</a></div> Am Di., 28. Dez. 2021 um 16:27 Uhr schrieb O.Hamann <o.ham...@gmx.net>: > And another idea: > > Did you try other more common ports, sth. like 8080 or so? > (in case there is some firewall mechanism blocking, or so?) > > Regards, Olaf > > > On 24.12.21 14:06, Thorsten Jolitz wrote: > > Hi List, > > I have the newest pil21 and the current picolisp wiki running on > > - Win10 / WSL2 (Debian unstable) > > - Archlinux > > and while in both cases I do see the start page of the wiki on > > http://localhost:5000, only the external Menu links work on WSL2, not > > the wiki internal links (nor the login). > > > > What is quite nice now, on Win10 I can access the running wiki server on > > localhost from WSL2/Debian (via W3M) and from the Windows browser > > (chrome or edge), I think that didn't work before. > > > > But these kind of links do not work in either case, > > <div id="menuLogin"><a > > href="-2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login">Log in</a></div> > > > > W3M says: "Can't load -2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login", while > > Edge shows "about:blank#blocked". I started the server in debug mode > > (pil wiki/main.l -main -go +), but no messages show up in the server > > window. > > > > Did anyone experience the same issue? > > Cheers > > Thorsten > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subjectUnsubscribe >