💾 Archived View for rawtext.club › ~sloum › geminilist › 001465.gmi captured on 2020-11-07 at 02:14:28. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2020-09-24)

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

<-- back to the mailing list

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

Luke Emmet luke at marmaladefoo.com

Tue Jun 9 21:29:20 BST 2020

- - - - - - - - - - - - - - - - - - - 

On 09-Jun-2020 21:26, solderpunk wrote:

On Tue, Jun 09, 2020 at 10:20:12PM +0200, Petite Abeille wrote:
Aha! I see what you mean now. Yes, this could be handled solely on the client side. Thanks for the clarification.
Still, no harm down if the fragment hit the server, right? Or?
I guess robust servers *should* tolerate this without throwing an error.
Cheers,
Solderpunk

Yes servers should definitely ignore any such fragment, which should *not* be sent to the server.

The query part of the URI is for server processing, the fragment is always client side only as far as I understand it.

https://en.wikipedia.org/wiki/Fragment_identifier

- L