Rack::Test does not default the Content-Type. about rack-test HOT 5 CLOSED

Although, I'm not sure if this should be added to Rack::MockResponse, or if it should be added at all. I suppose not adding a default Content-Type allows one to test whether an app is even specifying a custom Content-Type.

from rack-test.

Is a Content-Type header required by HTTP? I don't see anything saying it is.

If it's not required, I think rack-test should not handle it. (But, Sinatra, as a rack-test user, can default it to text/html because Sinatra is generally concerned with HTML).

Thoughts?

-Bryan

from rack-test.

HTTP doesn't require it in the general case, so I don't think rack-test should make any assumption about it. Even if HTTP did require it, I think rack-test shouldn't step forward and change it, because I might want to test my app for HTTP compliance, and I wouldn't want rack-test to give me false positives. In general, I want rack-test to give me exactly what the application-under-test would.

from rack-test.

This is fixed in rack edge, which has Rack::MockResponse inherit from Rack::Response, which properly handles headers with nil values. But it appears they still haven't released the new MockResponse in rack 1.2.2

from rack-test.

Closing for now, as it appears there's nothing actionable here. Please reopen if this is incorrect.

from rack-test.