[spec] What to do of fragments when there is a redirection

[Gary Johnson]

Stephane Bortzmeyer <stephane at sources.org> writes:

> Gemini specfication apparently does not mention what to do of
> fragments when there is a redirection.
>
> If original URI is <gemini://foobar.example/#baz> and there is a
> redirect to <gemini://thing.example/doit>, should the Gemini client
> consider is has to go to <gemini://thing.example/doit#baz> or to
> <gemini://thing.example/doit>?

This is a reasonable question. In HTTP, fragments are usually used to
denote a particular named anchor on the same page. While I support
parsing fragments from Gemini requests in my server and presenting them
to CGI-like functions, I don't include fragments in redirects to other
pages in the same way that I would leave off the query from one request
when redirecting to another page. AFAIK, both the query and fragment are
specific to a particular path on the server and don't transfer to
others.

Hopefully, Solderpunk can clarify this once and for all for us.

Best,
  Gary

-- 
GPG Key ID: 7BC158ED
Use `gpg --search-keys lambdatronic' to find me
Protect yourself from surveillance: https://emailselfdefense.fsf.org
=======================================================================
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Why is HTML email a security nightmare? See https://useplaintext.email/

Please avoid sending me MS-Office attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html