MAJOR: All HTML is shown as text about package.elm-lang.org HOT 8 CLOSED

Not reproducible here. Your example link http://package.elm-lang.org/packages/elm-lang/core/2.1.0/ gives good looking documentation pages for me (just checked) on my machine with all of:

• Firefox 39.0 (latest version it says)
• Chrome 44.0.2403.125 (latest version it says)
• Internet Explorer

from package.elm-lang.org.

Maybe there is a load balancer and a malfunctioning node. Can you check your response headers?

For me even with a simple curl, the response headers show this:

HTTP/1.1 200 OK
Date: Sat, 01 Aug 2015 11:18:44 GMT
Server: Snap/0.9.5.1
FFI-Control: Data
Content-Type: text/plain

I ran this command

curl -I http://package.elm-lang.org/packages/elm-lang/core/2.1.0/

from package.elm-lang.org.

The exact output of that command on my machine is:

HTTP/1.1 200 OK
Server: Snap/0.9.5.1
Date: Sat, 01 Aug 2015 11:29:44 GMT

from package.elm-lang.org.

So either the server I'm reaching is giving me a different response, or there is a man in the middle going on which is modifying my headers. This is why we need https everywhere...

from package.elm-lang.org.

When I browse on my phone or over tor there is no problem. Now I'm worried my ISP is doing something funky.

from package.elm-lang.org.

If you are comfortable, can you share any more details to help us know if this is specific to your computer? If it is specific, I am not sure if we have the power to resolve this.

from package.elm-lang.org.

Oh wow, today the problem has magically disappeared. This is a bit disturbing. Now it's not possible to do further investigation.

As for things you can do I can think of two options

1. Make *.elm-lang.org support https, that should avoid anyone messing with my http headers (although a good certificate might be expensive)
2. Make the server add an explicit content-type text/html, I think its good practice to include it if you can. I suspect that the problem doesn't occur when the content-type is set.

from package.elm-lang.org.

Okay, let's break those two suggestions out into issues of their own. Sounds like 2 is easy. No idea on 1, the answer may be "we don't have resources to do that right now"

from package.elm-lang.org.