[
https://issues.apache.org/jira/browse/COCOON-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alfred Nathaniel closed COCOON-2315.
------------------------------------
Resolution: Not A Problem
This is not a bug but a misconception what the file generator does. As the
name implies the file generator is most often used to read files, parse them as
XML documents and send the SAX events down the pipeline. The src attribute
also allows to use other source protocols as drop-in replacement for files.
In the case of http: the file generator creates a GET request to the given
webserver. Parameters or headers from the original request invoking the
current pipeline are not forwarded.
If you need to formulate customized HTTP requests you should look at
http://cocoon.apache.org/2.1/userdocs/wsproxy-generator.html.
> Generator and CInclude transformer do not include the request headers of the
> caller.
> ------------------------------------------------------------------------------------
>
> Key: COCOON-2315
> URL: https://issues.apache.org/jira/browse/COCOON-2315
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
> Affects Versions: 2.1.9, 2.1.12-dev (Current SVN)
> Reporter: Alec Bickerton
>
> When using the file generator or any sub class. The request headers are not
> propagated to the source.
> e.g.
> {code}
> <map:match pattern="deviceInfo">
> <map:generate src="http://deviceMetaService.example.com/lookup.jsp"/>
> <map:serialize/>
> </map:match>
> {code}
> The request received by the http://deviceMetaService.example.com/lookup.jsp
> will not contain the user-agent header of the original request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
