summaryrefslogtreecommitdiff
path: root/gopher
AgeCommit message (Collapse)Author
2023-09-07fix loop exit conditions on extended gophermap parsingtjpcc
2023-09-07execing included gophermapstjpcc
2023-09-07fix line number on error msgtjpcc
2023-09-07global-inclusiontjpcc
2023-09-07add the server host to gopher requeststjpcc
2023-09-07all the gopher CGI handlers to support gophernicus behaviorsv1.3.0tjpcc
2023-09-06contrib/fs.GuessGopherItemType -> gopher.GuessItemTypetjpcc
2023-09-03implement gophernicus extensions for gophermapstjpcc
2023-09-01refactor gophermap template handling and add markdown conversiontjpcc
2023-09-01gophermap->html conversion with overridable templatestjpcc
2023-08-31minor for loop cleanuptjpcc
2023-08-31a gopher MapDocument is a MenuTypetjpcc
2023-08-12Revert "text fixes"tjpcc
This reverts commit 7efdcf9277c4a7be88179cb93d309d2f1e684fe6. except the error text fix, keep that.
2023-08-12multi-protocol clienttjpcc
Fixes #4
2023-08-12move common types to an internal packagetjpcc
This helps avoid import cycles.
2023-08-12text fixestjpcc
* trying again with drone-ci and OmitHost * typo in the InvalidFingerQuery error message
2023-08-12add Fetch method to clients which follows redirectstjpcc
There are currently only gopher, gemini, and spartan clients. The finger client will have to implement this when it is written. The Fetch method takes the url as a string for convenience, and parses it into a URL for RoundTrip. Fixes #3
2023-05-09fix gopher request parsing for clients which don't send CRLFtjpcc
2023-05-03add JoinDefaultPort for servers' configurationtjpcc
2023-05-01name change gus -> slideruletjpcc
2023-02-15Switch Handler to an interface.tjpcc
HandlerFunc is much better as a function returning a Handler, rather than a newtype for the function type itself. This way there is no confusion creating a type-inferenced variable with HandlerFunc(func(... and then using a HandlerFunc where a Handler is expected. Much better to only have one public type.
2023-01-30finger protocoltjpcc
2023-01-28gopher support.tjpcc
Some of the contrib packages were originally built gemini-specific and had to be refactored into generic core functionality and thin protocol-specific wrappers for each of gemini and gopher.