EHC ❯ Overriden Content-type header when ContentType is not set

• Type: Bug
• Status: Closed
• Priority:
• Resolution: Fixed
• Component/s:
• Labels:

• Assignee: drb
• Reporter: sourceforgetracker
• Created: September 21, 2009
• Votes: 0
• Watchers: 0
• Updated:

  September 22, 2009
• Resolved:

  September 22, 2009

Description

If an HTTP response has its Content-type header set via directly calling setHeader(“Content-type”, <…>) on an HttpServletResponse instead of calling setContentType, the Content-type header will be ignored when serving the cached response, because HttpServletResponse’s setContentType will be called nevertheless by CachingFilter::setContentType. Sourceforge Ticket ID: 2620231 - Opened By: cataphract - 20 Feb 2009 15:11 UTC

Comments

Fiona OShea 2009-09-22

Re-opening so that I can properly close out these issues and have correct Resolution status in Jira