It was thus said that the Great Bj?rn W?rmedal once stated: > How does a client handle a link like the following: > => essays/why-spaces-are-%20-in-URLs.gmi > > The assumption here is that the author has not percent encoded > themselves -- this is the actual filename, %20 and all. And speaking of this, test #31 of the Gemini Client Torture Test [1] has this exact case---the link contains characters that should be encoded but aren't. It's been interesting to see which clients get an error, and which ones encode the bad characters. And for this test, there is no right answer---it's there to inform implementors that you'll encounter wrong stuff all the time, and you better be prepared to do *something* [2]. -spc [1] gemini://gemini.conman.org/test/torture/0031 [2] Not withstanding the advice I presented in my previous reply to this. Sometimes, crashing *is* a valid response to some unknown state, but it really depends upon the context of the program [3]. [3] I can expand on this if anyone cares.
---
Previous in thread (21 of 34): 🗣️ Sean Conner (sean (a) conman.org)
Next in thread (23 of 34): 🗣️ Jason McBrayer (jmcbray (a) carcosa.net)