You are viewing a plain text version of this content. The canonical link for it is here.
Posted to portalapps-dev@portals.apache.org by "Woonsan Ko (JIRA)" <ji...@apache.org> on 2015/12/21 22:41:46 UTC
[jira] [Assigned] (APA-72) No cookie rewriting
[ https://issues.apache.org/jira/browse/APA-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Woonsan Ko reassigned APA-72:
-----------------------------
Assignee: Woonsan Ko (was: David Sean Taylor)
> No cookie rewriting
> -------------------
>
> Key: APA-72
> URL: https://issues.apache.org/jira/browse/APA-72
> Project: Portals Apps
> Issue Type: Bug
> Components: apa-webcontent
> Affects Versions: apa-webcontent-2.0
> Reporter: Sascha Arndt
> Assignee: Woonsan Ko
>
> I have a problem using this maven dependency:
> {code:xml}
> <dependency>
> <groupId>org.apache.portals.applications</groupId>
> <artifactId>apa-webcontent2-reverse-proxy</artifactId>
> <version>2.0</version>
> </dependency>
> {code}
> Using this version of apa-webcontent2-reverse-proxy none of my cookies got rewrited or send back to the client. After some debugging session I found out, that the CloseableHttpClient and the ProxyContext were using different CookieStore objects.
> I "patched" it locally replacing "InitHttpClientCommand"s executeInternal-method like this:
> {code:title=InitHttpClientCommand.java|borderStyle=solid}
> @Override
> protected boolean executeInternal(final ProxyContext context) throws ReverseProxyException, IOException {
> CookieStore cookieStore = new BasicCookieStore();
> CloseableHttpClient httpClient = httpClientBuilder.setDefaultCookieStore(cookieStore).build();
> context.setCookieStore(cookieStore);
> context.setHttpClient(httpClient);
> return false;
> }
> {code}
> Is this a bug, or am I using it wrong?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)