You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hiram Chirino (JIRA)" <ji...@codehaus.org> on 2010/02/22 00:40:55 UTC

[jira] Commented: (WAGON-273) Default the HTTP cookie policy to BROWSER_COMPATIBILITY

    [ http://jira.codehaus.org/browse/WAGON-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210989#action_210989 ] 

Hiram Chirino commented on WAGON-273:
-------------------------------------

Looks like WAGON-269 tried to fix this issue but it has not.  I commented on that issue. 

> Default the HTTP cookie policy to BROWSER_COMPATIBILITY
> -------------------------------------------------------
>
>                 Key: WAGON-273
>                 URL: http://jira.codehaus.org/browse/WAGON-273
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-http
>            Reporter: Hiram Chirino
>             Fix For: 1.0
>
>         Attachments: patch
>
>
> Kinda related to WAGON-269.  Lots of websites these days (even google) are setting Cookies with domains like .google.com
> The HTTP commons folks disagree with what all browsers do and allow that to match the google.com domain.  I think most folks accept what most browsers do is the right thing even though it goes against what the Cookie RFC says
> I think it would behoove us to use the more relaxed BROWSER_COMPATIBILITY mode as the default as that will lower your support questions when wagon is used against domains that do this kind of thing.
> Patch of this change attached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira