You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Alfred Nathaniel (JIRA)" <ji...@apache.org> on 2011/09/23 18:18:26 UTC
[jira] [Updated] (COCOON-2315) WebserviceGenerator should allow to
include the request headers of the caller.
[ https://issues.apache.org/jira/browse/COCOON-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alfred Nathaniel updated COCOON-2315:
-------------------------------------
Summary: WebserviceGenerator should allow to include the request headers of the caller. (was: Generator and CInclude transformer do not include the request headers of the caller.)
That looks as if you expect Cocoon to act as forward proxy. I suggest you send a description of the actual problem to users@cocoon.apache.org.
> WebserviceGenerator should allow to 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