A client SHOULD NOT send the fragment part of a URL to the server?

On Tue, Jun 09, 2020 at 09:46:56PM +0200, Petite Abeille wrote:
> "A client SHOULD NOT send the fragment part of a URL to the server."
> -- Sean Conner, Resource request format for Gemini' states, circa 2019-08-01
> https://portal.mozz.us/gemini/gemini.conman.org/gRFC/0002
> 
> Such restriction is not reflected in the spec itself.
> 
> At the same time, the spec mentions header lines as "machine-readable 
representation of the internal structure of the document".
> 
> Could one reflect such structure using fragments?
> 
> E.g.:
> 
> gemini://gemini.circumlunar.space/docs/specification.gm#5.4+Core+line+types
> 
> Part of the gemini canon?

It's certainly something people have suggested.  I guess to make it work
reliably would require a very strict specification of how to transform
headings into fragments, which sounds fiddly and dull...

Either that, or we allow just numeric fragments like 3.2, which the
client is supposed to map to the second subsection of the third section.

Sounds like a pain to implement in terminal clients, at least.

Cheers,
Solderpunk

---

Previous in thread (1 of 12): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)

Next in thread (3 of 12): 🗣️ Matthew Graybosch (hello (a) matthewgraybosch.com)

View entire thread.