Would it be possible to remove the HTTP header that declares the content as “nosniff”? It’s purpose isn’t very useful (sniffing will give text/html anyway) and it triggers a bug in the BeOS NetPositive browser that makes it think the page from discuss.haiku-os.org is of type nosniff, rather than text/html, so it doesn’t display the page.
It’s probably a setting in the web server configuration, or maybe the Discuss system sets it. The headers currently include “X-Content-Type-Options: nosniff” as you can see:
/tmp> wget --verbose --server-response http://discuss.haiku-os.org/
–2016-08-24 16:04:12-- http://discuss.haiku-os.org/
Resolving discuss.haiku-os.org (discuss.haiku-os.org)… 78.46.196.115
Connecting to discuss.haiku-os.org (discuss.haiku-os.org)|78.46.196.115|:80… connected.
HTTP request sent, awaiting response…
HTTP/1.1 301 Moved Permanently
Server: nginx/1.10.1
Date: Wed, 24 Aug 2016 20:04:13 GMT
Content-Type: text/html
Content-Length: 185
Connection: keep-alive
Location: https://discuss.haiku-os.org/
Location: https://discuss.haiku-os.org/ [following]
–2016-08-24 16:04:13-- https://discuss.haiku-os.org/
Connecting to discuss.haiku-os.org (discuss.haiku-os.org)|78.46.196.115|:443… connected.
HTTP request sent, awaiting response…
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 24 Aug 2016 20:04:13 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Discourse-Route: list/latest
X-Discourse-Cached: true
X-Request-Id: f5947d38-2748-4261-af56-65be2eaf9752
X-Runtime: 0.002180
X-UA-Compatible: IE=edge
Length: unspecified [text/html]
Saving to: ‘index.html’
index.html [ <=> ] 67.09K --.-KB/s in 0.1s
2016-08-24 16:04:14 (506 KB/s) - ‘index.html’ saved [68702]