Issue #1 resolved

No content type set in StatusApp

Anonymous created an issue

In most cases, the StatusApp is not getting a content-type assigned. Most browsers likely don't choke on this, but unit tests with WebTest certainly do.

Comments (4)

  1. Luke Arno repo owner

    I spoke a little quickly. Of course it will not return a content-type for a 304 (per rfc2616). Allowed header was not used with 405s either, so fixing that too.

  2. Log in to comment