[ https://issues.apache.org/jira/browse/TRINIDAD-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott O'Bryan resolved TRINIDAD-2498. ------------------------------------- Resolution: Fixed Fix Version/s: 2.1.1-core > ResourceServlet does not preserve outgoing headers from URLConnection. > ---------------------------------------------------------------------- > > Key: TRINIDAD-2498 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2498 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Infrastructure > Affects Versions: 2.1.0-core > Reporter: Scott O'Bryan > Assignee: Scott O'Bryan > Fix For: 2.1.1-core > > Attachments: trin-patch.patch > > > The ResourceServlet relies on ResourceHandlers to supply things like graphics > images and the like to the browser. For most trinidad resources, these will > be local resources where headers other the cache-control and whatnot are > unimportant. > There might be ResourceHandler's, however, which do need these headers to be > preserved, for instance if a content-disposition header is returned. Since > the ResourceHandler provides a URLConnection, and there is header support > built into the URLConnection object, then ResourceServlet should be enhanced > to preserve a white-list of these headers. > For current implementation which don't have any extra headers, everything > should continue to work as it does today. -- This message was sent by Atlassian JIRA (v6.2#6252)