On Sun, Sep 26, 2021 at 08:30:31PM +0200, Stephane Bortzmeyer <stephane@sources.org> wrote a message of 8 lines which said: > It seems there is a specific brand of server that immediately resets > the connection when you ask a non-existing file (such as robots.txt) > instead of replying with 51. > > You can find it for instance at fulton.software, blog.snowfrost.garden > or cee64.us. > > Any idea what it is? Eleven capsules has apparently this issue (they probably all run the same software): gemini.real-ity.com gmni.kizaing.ca stillspinning.cc lertsenem.com iich.space capsule.adrianhesketh.com gemini.barca.mi.it tryops.net fulton.software lord.re cee64.us Robert khuxkm Miles suggests: The culprit seems to be the blog software written by Fulton (presumably of fulton.software)[1]. While Fulton's `rfs` server correctly handles non-existant files[2], `blog` lacks the final `header 51 'File not found'` of `rfs`. Thus, when `blog` terminates with no input, the connection is reset with no output. I would presume that this is the same issue plaguing cee64.us, given the similarity of their main page to Fulton's own fulton.software, and the same issue plaguing blog.snowfrost.garden, which seems to be running a modified version of `blog`, if it is running one at all. If blog.snowfrost.garden isn't in fact running `blog`, I would presume the issue to be a similar omission of the final `header 51 'File not found'` in whatever their software is written in. [1]: https://git.sr.ht/~fultonbrowne/g9srv/tree/master/item/blog [2]: https://git.sr.ht/~fultonbrowne/g9srv/tree/master/item/rfs
---
Previous in thread (4 of 5): 🗣️ Jacob Stewart (jacob.stewart (a) tutamail.com)