container: fall back to text/plain instead of application/octet-stream

This has its own problems, but application/octet-stream has the horrible
consequence that opening any local file with an unrecognized type
automatically quits the browser.

(FWIW, w3m also falls back to text/plain, so it's not such an unreasonable
default.)

The proper solution would be to a) fix the bug that makes the browser
auto-quit and b) show a "what to do" prompt for unrecognized file types
(and allow users to override it, preferably on a per-protocol basis.)

1 files changed, 2 insertions, 1 deletions

diff --git a/src/local/container.nim b/src/local/container.nim
index 011c7279..62799c56 100644
--- a/src/local/container.nim
+++ b/src/local/container.nim
@@ -1412,7 +1412,8 @@ proc applyResponse*(container: Container; response: Response;
   if container.contentType.isNone:
     var contentType = response.getContentType()
     if contentType == "application/octet-stream":
-      contentType = mimeTypes.guessContentType(container.url.pathname)
+      contentType = mimeTypes.guessContentType(container.url.pathname,
+        "text/plain")
     container.contentType = some(contentType)
   # setup charsets:
   # * override charset