Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Tue, 4 Dec 2012 13:22:58 +0000 (UTC)
From: "Oleg Kalnichevski (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <730497216.58794.1354627378473.JavaMail.jiratomcat@arcas>
In-Reply-To: <780432049.51516.1354493878361.JavaMail.jiratomcat@arcas>
Subject: [jira] [Resolved] (HTTPCLIENT-1267) There seems to be no way to get
 HttpClient to include cookies from a custom store
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCLIENT-1267.
-------------------------------------------

    Resolution: Invalid

> We do not care at all what kind of cookie it is; 

But you should, because cookie representations differ.

> If you have a way of saving the cookie in its original form and reconstituting a Cookie object from it that can be retransmitted to the server, that would be infinitely preferable to needing to figure out what kind of cookie it is etc. That was never the goal here.

Java serialization is supported out of the box. We could support another serialization mechanisms as long as they do not require additional dependencies.

Oleg
                
> There seems to be no way to get HttpClient to include cookies from a custom store
> ---------------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1267
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1267
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpCookie
>    Affects Versions: 4.2.2
>            Reporter: Karl Wright
>
> In the port of ManifoldCF from commons-httpclient to httpcomponents, we discovered a problem or maybe a design flaw with how cookies are handled.
> What we're trying to do is to follow a certain series of html pages, and record the cookies after that is done, and use exactly those cookies for a subsequent series of pages.  So I have code that looks something like this:
> {code}
> DefaultHttpClient httpClient = new DefaultHttpClient();
> ...
> CookieStore cs = new BasicCookieStore();
> cs.addCookie(...);  // for each saved cookie
> httpClient.setCookieStore(cs);
> HttpGet httpget = new HttpGet(...);
> HttpResponse response = httpClient.execute(httpget);
> Cookie[] cookiesToSave = httpClient.getCookieStore().getCookies();
> [save the cookies aside]
> {code}
> What happens when I do this against a page that sets a cookie, is I get a perfectly reasonable cookie, and save it.  For the next page, the code to add the cookie to the custom store then seems to work fine as well.  But when I watch what is transmitted for the request (via header logging) I see no Cookie header being sent, and indeed the cookie seems to be lost.
> Similar logic was done with HttpState in commons-httpclient, and worked perfectly there against the same website.
> I have not yet tried the HttpContext approach for implementing this - I may try that while awaiting an answer to this ticket, but the above seems like it ought to work, according to the documentation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org