[jira] Commented: (COCOON-1624) reader caching does not consider mime-type

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COCOON-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463510 ] 

Carsten Ziegeler commented on COCOON-1624:
------------------------------------------

I think we have to fix this in the pipeline implementations. A reader never gets the configured mime-type from the sitemap.
I guess we have to improve our caching implementations to better support mime-types (and perhaps http headers) anyway.

> reader caching does not consider mime-type
> ------------------------------------------
>
>                 Key: COCOON-1624
>                 URL: https://issues.apache.org/jira/browse/COCOON-1624
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Jörg Heinicke
>         Assigned To: Cocoon Developers Team
>
> Changing the mime type on a reader in a caching pipeline does not invalidate its
> former usage with another mime type.
> Sample:
> <map:match pattern="form1.xul">
>   <map:read src="forms/form1_template.xul" mime-type="text/xml"/>
> </map:match>
> changed to
> <map:match pattern="form1.xul">
>   <map:read src="forms/form1_template.xul"
> mime-type="application/vnd.mozilla.xul+xml"/>
> </map:match>
> still results in delivery with text/xml. Carsten already saw it at the hackathon
> when I played around with XUL.
> Jörg

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira