Return-Path: Delivered-To: apmail-jakarta-httpclient-dev-archive@www.apache.org Received: (qmail 89286 invoked from network); 17 Apr 2006 20:59:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Apr 2006 20:59:43 -0000 Received: (qmail 42389 invoked by uid 500); 17 Apr 2006 20:59:43 -0000 Delivered-To: apmail-jakarta-httpclient-dev-archive@jakarta.apache.org Received: (qmail 42357 invoked by uid 500); 17 Apr 2006 20:59:42 -0000 Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "HttpClient Project" Reply-To: "HttpClient Project" Delivered-To: mailing list httpclient-dev@jakarta.apache.org Received: (qmail 42346 invoked by uid 99); 17 Apr 2006 20:59:42 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Apr 2006 13:59:42 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,MSGID_FROM_MTA_HEADER,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mikebingen@hotmail.com designates 65.54.224.24 as permitted sender) Received: from [65.54.224.24] (HELO hotmail.com) (65.54.224.24) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Apr 2006 13:59:42 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 17 Apr 2006 13:59:21 -0700 Message-ID: Received: from 65.54.224.200 by by105fd.bay105.hotmail.msn.com with HTTP; Mon, 17 Apr 2006 20:59:17 GMT X-Originating-IP: [71.146.149.100] X-Originating-Email: [mikebingen@hotmail.com] X-Sender: mikebingen@hotmail.com From: "Monkey Mike" To: httpclient-dev@jakarta.apache.org Subject: HttpClient Cookie confusion Date: Mon, 17 Apr 2006 13:59:17 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 17 Apr 2006 20:59:21.0824 (UTC) FILETIME=[CD0E1600:01C66261] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Mr. Oleg Kalnichevski and others... Hi! My name is Mike Uehara-Bingen, I am one of the head programmers at Yowza Software, and I am new to this mailing list. We have been working on a new application for a little over a year now, and I've recently started using HttpClient for one of our very important sub-projects. I started by doing this sub-project in Perl's LWP, and everything was working great. After considering some security issues, however, we've decided that this sub-project should be kept in Java (most of the rest of the project is written in Java), and so I started translating my Perl code into Java code. Basically, since Java will eventually handle all the data that is retrieved from servers, and since this data is a security risk, we want the data to go directly into the JVM...and if we use Perl to retrieve the data then the data would either have to be written to disk or to STDOUT in order to pass it to Java. Let me take a moment to say thanks for you and your colleagues' work on HttpClient. It is fast, easy to use, and very useful. Of course, admittedly, I wouldn't be writing you if I wasn't having a problem! One thing that has been making things difficult is HttpClient's requirement that cookies follow the various standards. My client will be interacting with lots of different servers that do not follow these cookie standards, and so I really wish I could set the Cookie Policy as lenient as possible. To my knowledge, the following Cookie Policies are available... CookiePolicy.BROWSER_COMPATIBILITY CookiePolicy.NETSCAPE CookiePolicy.RFC_2109 CookiePolicy.DEFAULT CookiePolicy.IGNORE_COOKIES I've also tried... hclClient.getParams().setCookiePolicy( null ); ( ...where "hclClient" is the instance of HttpClient ) In all of these cases, I still get "Cookie Rejected" warnings for various reasons. I realize that the servers are breaking the rules, but I don't have control over these servers and so I have to be able to handle whatever they throw at me. It was interesting to see that HttpClient imposes these restrictions on the Cookie handling, as Perl's LWP does not. I've had to set a few of my own cookies here and there in both LWP and HttpClient because they are cookies that are normally set via javascript, but never have I had to consider whether or not cookies are following standards. So is there a way to turn off these restrictions? Or is there something else that I might be doing wrong? Any help that you could provide would be much appreciated. Thanks! :) -Mike Uehara-Bingen Yowza Software mike@yowzasoftware.com --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org