Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6B2FEDB98 for ; Thu, 22 Nov 2012 13:31:08 +0000 (UTC) Received: (qmail 63108 invoked by uid 500); 22 Nov 2012 13:31:08 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 62770 invoked by uid 500); 22 Nov 2012 13:31:03 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 62641 invoked by uid 99); 22 Nov 2012 13:30:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Nov 2012 13:30:59 +0000 Date: Thu, 22 Nov 2012 13:30:59 +0000 (UTC) From: "Oleg Kalnichevski (JIRA)" To: dev@hc.apache.org Message-ID: <403648773.16875.1353591059702.JavaMail.jiratomcat@arcas> In-Reply-To: <615933728.12273.1353505558205.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (HTTPCLIENT-1264) Need CookiePolicy.BROWSER_COMPATIBILITY_MEDIUM_SECURITY policy MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HTTPCLIENT-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski updated HTTPCLIENT-1264: ------------------------------------------ Fix Version/s: 4.3 Final Karl The trouble is that an additional policy would need to be properly documented and maintained afterwards. I am desperately trying to reduce the footprint of the public APIs and the set of configuration options supported out the box, because it is enormously difficult to maintain such a significant code base with so few people working on the project in their fee time. I would be very strongly in favor of doing a proper analysis and amending the default implementation. Besides, next feature release would be a good moment for tweaking the behavior of compatibility cookie spec given the scope of changed planned for 4.3. I am having my hands full with 4.3 development and have no bandwidth left for this issue. However, I'll happily contribute in terms of code reviews, patching and so on. Oleg > Need CookiePolicy.BROWSER_COMPATIBILITY_MEDIUM_SECURITY policy > -------------------------------------------------------------- > > Key: HTTPCLIENT-1264 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1264 > Project: HttpComponents HttpClient > Issue Type: Improvement > Components: HttpClient > Affects Versions: 4.2.2 > Reporter: Karl Wright > Fix For: 4.3 Final > > > The ManifoldCF project is currently moving to HttpComponents 4.2.2 from a heavily patched commons-httpclient 3.1 version. One of the patches seems to have no particular equivalent yet in HttpComponents. Please see CONNECTORS-119 for details about what the patch did, and research into the current HttpComponents code base. > I am happy to create a specific patch if that is desired; please let me know. -- 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