💾 Archived View for gemi.dev › gemini-mailing-list › 000185.gmi captured on 2023-11-04 at 12:31:21. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
I'm going through the logs for my Gemini server, specifically errors, and while the majority due to clients hitting some corner cases in references, there are a few that really stick out to me. There are the 27 requests for "favicon.txt", and I have to wonder what's up with that? The file is "favicon.ico". I suppose I could return the .ico file for any reference to "favicon.*" but I think that might be too cruel. Then there are the 5 requests for "c2lnaWwlM0". No clue on that one either. And then there's the 2 requests for "http://www.conman.org". I'm sorry, but the web server is over there, at port 80. -spc
It's Michael's (mozz) draft RFC for an emoji based favicon for Gemini. See gemini://mozz.us/files/rfc_gemini_favicon.gmi . There was also a gemlog post about it. makeworld ??????? Original Message ??????? On Saturday, June 6, 2020 4:55 PM, Sean Conner <sean at conman.org> wrote: > I'm going through the logs for my Gemini server, specifically errors, and > while the majority due to clients hitting some corner cases in references, > there are a few that really stick out to me. > > There are the 27 requests for "favicon.txt", and I have to wonder what's > up with that? The file is "favicon.ico". I suppose I could return the .ico > file for any reference to "favicon.*" but I think that might be too cruel. > > Then there are the 5 requests for "c2lnaWwlM0". No clue on that one > either. > > And then there's the 2 requests for "http://www.conman.org". I'm sorry, > but the web server is over there, at port 80. > > -spc
> On Jun 6, 2020, at 22:55, Sean Conner <sean at conman.org> wrote: > > I'm going through the logs for my Gemini server, specifically errors, and > while the majority due to clients hitting some corner cases in references, > there are a few that really stick out to me. Talking of which, should Gemini servers adopt the /.well-known/ convention [1][2][3]? Including for robots.txt, favicon.ico, etc, etc, etc... [1] https://en.wikipedia.org/wiki/List_of_/.well-known/_services_offered_by_webservers [2] https://tools.ietf.org/html/rfc8615 [3] https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml
It was thus said that the Great colecmac at protonmail.com once stated: > It's Michael's (mozz) draft RFC for an emoji based favicon for Gemini. > > See gemini://mozz.us/files/rfc_gemini_favicon.gmi . There was also a > gemlog post about it. Ah. Okay. I'll play along then. -spc
It was thus said that the Great Petite Abeille once stated: > > > > On Jun 6, 2020, at 22:55, Sean Conner <sean at conman.org> wrote: > > > > I'm going through the logs for my Gemini server, specifically errors, and > > while the majority due to clients hitting some corner cases in references, > > there are a few that really stick out to me. > > Talking of which, should Gemini servers adopt the /.well-known/ convention [1][2][3]? Should? I don't see why not. > Including for robots.txt, favicon.ico, etc, etc, etc... Well, the list of registered well known URLs don't include any of those, so I'm not sure of the utility, but ... okay? -spc > [1] https://en.wikipedia.org/wiki/List_of_/.well-known/_services_offered_by_webservers > [2] https://tools.ietf.org/html/rfc8615 > [3] https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml
---
Previous Thread: First Gemini CGI application in Rebol
Next Thread: [Ann] An online arithmetic calculator for Gemini