Scheme Section 2 quibble

On Wed, Nov 18, 2020 at 4:10 PM Sean Conner <sean at conman.org> wrote:
>
> It was thus said that the Great Remco once stated:
> >
> > If you want to point fingers:
> >
> > https://github.com/michael-lazar/gemini-diagnostics/blob/master/gemini-
diagnostics#L440
> >
> > That's what I based my implementation on and I suspect many others did
> > so too.
>
>  The test isn't *wrong* per se, it's just testing at the wrong level. My
> server will return:
>
>     gemini://gemini.conman.org   -> 20
>     gemini://gemini.conman.org/   -> 20
>
> but
>
>     gemini://gemini.conman.org/test -> 31 gemini://gemini.conman.org/test/
>
>   which is what that test is testing.
>
>   -spc

Yes that's probably what I meant to do. It was difficult to write many of the
tests because they can't assume that any particular directory exists on the
server. I didn't realize that the root URL was special in this regard.

I think this is an interesting problem for the gemini protocol. In HTTP you
typically only have one way to write out this request so it's never a problem:

GET / HTTP/1.1

Even though "gemini://example.com" and "gemini://example.com/" are supposed to
be identical per the URL definition, good luck getting gemini developers to
read through 100+ pages of RFCs and implement this correctly.

- Michael

---

Previous in thread (30 of 31): 🗣️ Sean Conner (sean (a) conman.org)

View entire thread.