SPEC in rack-1.3.10 vs SPEC in rack-1.4.0

- old
+ new

@@ -144,22 +144,20 @@ consisting of lines (for multiple header values, e.g. multiple <tt>Set-Cookie</tt> values) seperated by "\n". The lines must not contain characters below 037. === The Content-Type There must be a <tt>Content-Type</tt>, except when the -+Status+ is 1xx, 204 or 304, in which case there must be none ++Status+ is 1xx, 204, 205 or 304, in which case there must be none given. === The Content-Length There must not be a <tt>Content-Length</tt> header when the -+Status+ is 1xx, 204 or 304. ++Status+ is 1xx, 204, 205 or 304. === The Body The Body must respond to +each+ and must only yield String values. The Body itself should not be an instance of String, as this will break in Ruby 1.9. -If the Body responds to +close+, it will be called after iteration. If -the body is replaced by a middleware after action, the original body -must be closed first, if it repsonds to close. +If the Body responds to +close+, it will be called after iteration. If the Body responds to +to_path+, it must return a String identifying the location of a file whose contents are identical to that produced by calling +each+; this may be used by the server as an alternative, possibly more efficient way to transport the response.