Comment by 🦂 zzo38
I think that most URLs should work with both TLS and non-TLS (with the exception of files requiring user authentication, so those files (only) might require TLS), so that is not wrong; there dies not seem to be much point for disallowing TLS for some files even though other files on the same server do allow TLS. However, as I had mentioned elsewhere, the gopher menu format does not indicate if it is TLS or not. Links to the same host and port could use TLS or not depending on the current URL, but for external links, DNS records could be used to decide. There could be a user configuration setting to control this feature.
Mar 09 · 8 weeks ago
2 Later Comments ↓
🍀 gritty [OP] · Mar 09 at 19:27:
yeah I'm not really sure why. There isn't really an official spec so maybe this wasn't considered.
@zzo38 Right. I forgot the gopher menu format can't specify TLS. I might just do a host-based thing for now. It appears there's a gopher client that does TOFU. Always something.
Original Post
what is "gophers://" ?