[
https://issues.apache.org/jira/browse/HTTPCLIENT-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649680#comment-13649680
]
Karl Wright commented on HTTPCLIENT-1264:
-----------------------------------------
bq. Do we really need two policies active by default, though? When appropriate
one can register it as 'browser default' policy. Would it be OK with you to not
register the medium security policy by default?
Hi Oleg,
In general I'm fine with your suggestion. But now I am unclear as to the
criteria we use to decide whether a policy should be preregistered or not.
Perhaps it would be good to explain your thinking here.
> 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
> Assignee: Karl Wright
> Fix For: 4.3 Final
>
> Attachments: HTTPCLIENT-1264.patch, HTTPCLIENT-1264.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
