[terinjokes]

Must have been a temporary problem, seems like it's sending the correct headers now.

(For the record, I had the problem in both Chrome and Firefox)