💾 Archived View for gem.benscraft.info › mailing-list › messages › 247 captured on 2021-12-05 at 23:47:19. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-12-03)

-=-=-=-=-=-=-

Re: [tech] IPv6 addresses in URLs

- nervuri <nervuri at disroot.org>

@ Fri, 16 Apr 2021 12:23 +0000

Full Thread

Reply to Stephane Bortzmeyer <stephane at sources.org>

────────────────────────────────────────────────────────────────────────────────

https://gitlab.com/gemini-specification/protocol/-/issues/33

See makeworld's comments. It looks like "no SNI" is the right answer

for IP addresses.

On Fri, 2021-04-16, Stephane Bortzmeyer wrote:

> gemini://2a02:7b40:592f:a446::1/
> gemini://[2a02:7b40:592f:a446::1]:1965/
No. The first one is not a legal URL.

Thanks, I stand corrected. Indeed, Agunua points out that the first URL

is invalid, but connects to the second one.

The clients I tested which didn't accept the second URL are:

- Lagrange

- gmni

- bombadillo

- Mozz web proxy - https://portal.mozz.us/gemini/%5B2a02:7b40:592f:a446::1%5D:1965/

- gemini://celehner.com/proxy/ - https://celehner.com/gemini://[2a02:7b40:592f:a446::1]:1965/

- https://gemini.susa.net:1993/proxy.html

However, most clients accept the host without the scheme and behavior is

sometimes inconsistent. For instance, in Amfora:

- "89.47.164.70" works

- "[2a02:7b40:592f:a446::1]" works if it is supplied from the

command line, but not from within the program.

- "2a02:7b40:592f:a446::1" - same as the above

Agunua and Kristall adhere to the RFC, so they connect to the first two,

but not the third.

════════════════════════════════════════════════════════════════════════════════

Replies

Reply from Michael Lazar <lazar.michael22 at gmail.com>