@rickmoynihan: I would expect the wrap-file-info
to keep an existing content-type header untouched.
"This middleware is deprecated. Prefer the ring.middleware.content-type and ring.middleware.not-modified middleware instead."
wrap-content-type
behaves sane and does not touch the response when there is a content-type header set.
@ordnungswidrig: it doesn't if you return a file as :body
- if you return anything else e.g.a string it preserves it
which „it“? wrap-file-info
or wrap-content-type
? :simple_smile:
the deprecated wrap-file-info