You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested #703 on a fresh server and chose not to buy an IPv4 address because, well, we're out and reusing someone else's costs extra nowadays.
Address encoding issue 1
Navigate to http://[2a01:4f8:c17:cfd5::1]/
Firefox reports a protocol error. Wireshark shows this HTTP response:
HTTP/1.0 302 FoundDate: Sun, 15 Oct 2023 14:03:07 GMTServer: Apache/2.4.57 (Debian)Cache-Control: no-cache, privateLocation: http://%5B2a01:4f8:c17:cfd5::1%5D/setup/startConnection: closeContent-Type: text/html; charset=UTF-8<!DOCTYPE html><html><head><meta charset="UTF-8" /><meta http-equiv="refresh" content="0;url='http://%5B2a01:4f8:c17:cfd5::1%5D/setup/start'" /><title>Redirecting to http://%5B2a01:4f8:c17:cfd5::1%5D/setup/start</title></head><body>Redirecting to <a href="http://%5B2a01:4f8:c17:cfd5::1%5D/setup/start">http://%5B2a01:4f8:c17:cfd5::1%5D/setup/start</a>.</body></html>
(Note: if you see red highlighted lines, that's github's broken http syntax parsing or something, not me trying to indicate where the error is. It seems to think that HTTP has only headers, no status line or body!)
Address encoding issue 2
Navigate to http://[2a01:4f8:c17:cfd5::1]/setup/start
Note: the JavaScript console reports that document.querySelector('meta[property="la-app-data"]') returns null from resources/assets/js/components/Base.js, not sure what that's used for
Click the continue button ("Check Requirements") which is an <a href='http://%5B2a01:4f8:c17:cfd5::1%5D/setup/requirements'>
Firefox ignores the click altogether
All other links are also broken, for example the main menu on the guest page.
$ wget https://github.com/Kovah/LinkAce/releases/download/v1.12.2/linkace-v1.12.2.zip
--2023-10-15 14:01:32-- https://github.com/Kovah/LinkAce/releases/download/v1.12.2/linkace-v1.12.2.zip
Resolving github.com (github.com)... 140.82.121.4
Connecting to github.com (github.com)|140.82.121.4|:443... failed: Network is unreachable.
Linkace.org and demo.linkace.org work perfectly fine via the v6-only connection (tested by using ssh -D 0:8080 with that IPv6-only server and configuring that as socks5+dns proxy in Firefox), so those could be used as distribution method.
As an aside, the zip structure is a bit convoluted: linkace-v1.12.2.zip contains another zip file called linkace.zip which contains a tarbomb (all files in . rather than in a subdirectory). I don't know about others, but for me it would be more expected to have the files contained in a subdirectory of the zip that one downloads.
The errors may stem from the same code: [] are incorrectly encoded somewhere. Where and why this happens, I don't know how to easily find out. For the first two encoding issues, a solution-by-simplification may be to just use relative URLs instead of trying to add unnecessary details to links, but that would still leave the link adding problem
LinkAce version: dev
Setup Method: PHP
Operating System: Debian Bookworm
The text was updated successfully, but these errors were encountered:
Forgot to mention: I'll leave that system up for a week or so, so you can see the problem for yourself and we can easily test a fix. I could add an ssh key (one of these? https://github.com/Kovah.keys) if you'd like to poke around yourself
Why am I doing this to myself 😭 An add-on to delete cookies after closing the tab now pops an error onto my screen every few minutes. Maybe that's what I had network.dns.disableIPv6 set to enabled in about:config for years ._. The world is clearly not ready for the wonders of IPv6
(Edit: for the record, nothing a little echo "delete from moz_cookies where host like '%4f8:c17:cfd5%';" | sqlite3 ~/.mozilla/*/cookies.sqlite couldn't fix ^^)
Thanks for the very detailed report. I will have a look at the parsing of URLs containing v6 IPs. But all the other stuff... well you mentioned it: the world is not ready yet. I can't understand how a dominating platform like Github does not support incoming IPv6 traffic...
I tested #703 on a fresh server and chose not to buy an IPv4 address because, well, we're out and reusing someone else's costs extra nowadays.
Address encoding issue 1
(Note: if you see red highlighted lines, that's github's broken http syntax parsing or something, not me trying to indicate where the error is. It seems to think that HTTP has only headers, no status line or body!)
Address encoding issue 2
document.querySelector('meta[property="la-app-data"]')
returnsnull
fromresources/assets/js/components/Base.js
, not sure what that's used for<a href='http://%5B2a01:4f8:c17:cfd5::1%5D/setup/requirements'>
All other links are also broken, for example the main menu on the guest page.
Installation issue
The documentation instructs one to "Download the LinkAce .zip package from the release page."
Linkace.org and demo.linkace.org work perfectly fine via the v6-only connection (tested by using
ssh -D 0:8080
with that IPv6-only server and configuring that as socks5+dns proxy in Firefox), so those could be used as distribution method.As an aside, the zip structure is a bit convoluted:
linkace-v1.12.2.zip
contains another zip file calledlinkace.zip
which contains a tarbomb (all files in.
rather than in a subdirectory). I don't know about others, but for me it would be more expected to have the files contained in a subdirectory of the zip that one downloads.Link adding issue
/etc/hosts
and navigate to the link adding page at e.g. http://linkacetest6.local/links/createhttp://[2a01:4f8:c17:cfd5::1]/
as the link and try to add itThe errors may stem from the same code:
[]
are incorrectly encoded somewhere. Where and why this happens, I don't know how to easily find out. For the first two encoding issues, a solution-by-simplification may be to just use relative URLs instead of trying to add unnecessary details to links, but that would still leave the link adding problemLinkAce version: dev
Setup Method: PHP
Operating System: Debian Bookworm
The text was updated successfully, but these errors were encountered: