Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence Woodman Newsgroups: comp.infosystems.gopher Subject: Re: morena.rip Date: Wed, 9 Oct 2024 10:29:39 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: References: <20241009120432.1aa13e7e@mateusz> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 09 Oct 2024 12:29:39 +0200 (CEST) Injection-Info: dont-email.me; posting-host="9ee081799c9425454c68efad8146767c"; logging-data="2759081"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19i4G1dXuhmM8Ef7LXIxZpmRJ5c3FrjIpU=" User-Agent: Pan/0.154 (Izium; 517acf4) Cancel-Lock: sha1:efnFDiHARWStZdV0Vq4yvixgAqU= Xref: csiph.com comp.infosystems.gopher:697 On Wed, 9 Oct 2024 12:04:32 +0200, Mateusz Viste wrote: > dn. Tue, 8 Oct 2024 21:45:14 -0000 (UTC), morena@morena.rip napisaƂ: > >> It's my pleasure to announce there is now only one true >> 100% RFC 1436 compliant gopher server morena.rip >> >> Only true UMN gopher client loves it when command is with >> the slash at the end. 'gopher gopher://morena.rip/' > > I'm not sure I understand the issue. Are some gopher clients failing > when the URL is trailed by a slash? I checked with gopherus right now, > seems to work fine: > > gopherus gopher://morena.rip/ It's an interesting one, considering that selectors shouldn't by default be thought of as a file path and therefore whether servers should strip leading and trailing slashes is debatable. That Morena and many servers do seems helpful if not arguably going against the RFC somewhat and possibly problematic if this behaviour isn't configurable. Lorry