A Cache-Control header with an empty string is meaningless (confusing, even, to those inspecting response headers) and slightly wasteful. Signed-off-by: Stephen Celis <firstname.lastname@example.org>
Update tests for Directory, ETag, File and Head.
…d also allow a default cache directive when no caching is done.
…as given. It is extremally important to mark these responses as private by default.
Signed-off-by: raggi <email@example.com>
The HTTP specification says that if both Last-Modified and ETag are sent, both should be matched in other to check if a request is fresh or not. If Rack always set ETag, even if Last-Modified is sent, checking the freshness according to specification becomes non trivial, since I will always need the digested body response. Signed-off-by: raggi <firstname.lastname@example.org>
…k spec requires strings.