Almanack/almnck
2
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Why won't it work in lynx/w3m? #2

New issue
Open
opened 2026-01-05 00:51:21 -08:00 by danny · 2 comments
danny commented 2026-01-05 00:51:21 -08:00
Owner
Copy link

I suspect the caddy proxy or some https voodo, as it works on the dev server

I suspect the caddy proxy or some https voodo, as it works on the dev server
danny commented 2026-01-12 02:45:54 -08:00
Author
Owner
Copy link

It's a problem with ipv6 -- ipv4 connections work fine. I think w3m may not check whether ipv6 is connected before trying.

It's a problem with ipv6 -- ipv4 connections work fine. I think w3m may not check whether ipv6 is connected before trying.
danny commented 2026-01-12 02:50:29 -08:00
Author
Owner
Copy link

(Google doesn't suffer this problem! Maybe it does not return a ipv6 address to non-ipv6 accessible IPs?)

(Google doesn't suffer this problem! Maybe it does not return a ipv6 address to non-ipv6 accessible IPs?)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/membership-core
feature/webgl-moon
feature/mechanism-shadows
feature/margin-box-positioning
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Almanack/almnck#2
No description provided.