Problem with probably malformed gophermap #241
|
Hi @davep, there is a problem with the link If rogallo can't parse or fix such things, it should catch the error and output an error message without aborting completely. There are probably more sites with such gophermaps, which don't have a <TAB> and the rest of a normal "i" type line, so you should investigate, and if possible, "repair" such malformed gophermaps. Keep up your wonderful work, |
Replies: 3 comments 4 replies
|
Yup, looks like there's a lot of I guess this is where I start rolling back being fairly strict about this stuff. ;-) |
|
Yes, it's not nice that you can't count on gopher server responses, and I believe its breaking with Gophers unwritten rules, but after all, they're rules not laws. And because it's such a seemingly simple protocol, there are also a lot of server implemetations, like this one. And some people might create their gophermaps manually, which is also error prone. So I would suggest, if your parser can't parse a real link line and make a functioning link from it, it should also ignore it, or better, print some information about that fact on the link line in question. |

The GopherMap v0.2.0 library fixes this, so if you can update the dependencies of Rogallo (
uv tool upgrade --allif you installed withuv, for example) this should work right now:I'll also make an update to Rogallo later on that bumps the minimum-required GopherMap library.