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

[John Cowan]

>
> Therefore, for HTTP, RFC 7231 has to describe in detail what the
> client ("user agent", in HTTP parlance) has to do with
> fragments. Should we consider that "in doubt, do as HTTP does?")
>

I think we should adopt the following RFC 7231 compatible rules.

0) The semantics of a fragment are defined solely by the media type of the
resource and not by the rest of the URL.

1) Clients MUST NOT send a fragment to the server.  If the server needs to
know the content of a fragment, it should be part of the path or the query
string instead.  This was a firm HTTP rule until fragments beginning with !
were invented, and IMO should be a firm Gemini rule.

2) If the client gets a redirect containing a fragment, the client MUST
apply this fragment when the redirected resource is retrieved, ignoring any
original fragment.

3) If the original URL has a fragment and the redirect doesn't, the client
MUST apply the original fragment when the redirected resource is retrieved.

4) Content authors MUST NOT put personally identifying information into
fragments, as they can be transferred from one host to another by the
operation of rule 3.



John Cowan          http://vrici.lojban.org/~cowan        cowan at ccil.org
He who would do good to another must do it in Minute Particulars;
General Good is the plea of the scoundrel, hypocrite and flatterer:
For Art and Science cannot exist but in minutely organized Particulars.
  --William Blake, il miglior fabbro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201222/ef94f595/attachment.htm>