BUGFIX: Content-Type, Nil Raw Body Edge Case, Links

FIXES:
* There was an edge case where a raw body for HTML would potentially
  result in a nil byte slice exception. This has been fixed.
  (I don't even know if it was possible, I just made sure it wasn't.)
* The links browser is now explicitly returned as HTML and properly
  detected as a "browser".
* Hyperlinks for links, w3m added to Usage page.
* Content-Type is now always set correctly; there were cases where it
  was improperly returning e.g. text/plain for JSON.
This commit is contained in:
brent saner
2024-12-19 02:27:53 -05:00
parent 8a0465a0f4
commit 6b75e17f48
5 changed files with 55 additions and 6 deletions

8
TODO
View File

@@ -1,3 +1,7 @@
- suggest browser, OS alternatives (again)
- link to ipinfo.io for client IP (again)
-- or just implement myself
- implement ipinfo.io equiv. myself?
- also link to https://www.useragentstring.com/
-- or maybe https://www.whatsmyua.info/
-- see https://www.useragentstring.com/pages/api.php
- note that though lynx and elinks are "graphical", links is considered text. w3m is considered graphical.
- fix the text/plain issue for the json (et. al.) renderer