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

Michael Osipov updated WAGON-528:
---------------------------------
    Description: HttpClient supports {{Accept-Encoding}} out of the box, there 
is no need to set it manually. Since this automatically adds {{deflate}} the 
lightweight provider should mimic this too. Compression support cannot be 
disabled on the lightweight provider thus to be consistent, it should be the 
same for the HttpClient provider, but since the latter provider is more 
versatile one could add {{<disableContentCompression />}} option to the 
{{settings.xml}} in another ticket.  (was: HttpClient supports 
{{Accept-Encoding}} out of the box, there is no need to set it manually. Since 
this automatically adds {{deflate}} the lightweight provider should mimic this 
too. Compression support cannot be disabled on the lightweight provider thus to 
be consistent, it should be the same for the HttpClient provider.)

> Extend and unify compression capabilities in HTTP (Lightweight) Wagon
> ---------------------------------------------------------------------
>
>                 Key: WAGON-528
>                 URL: https://issues.apache.org/jira/browse/WAGON-528
>             Project: Maven Wagon
>          Issue Type: Task
>          Components: wagon-http, wagon-http-lightweight
>    Affects Versions: 3.1.0
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.2.0
>
>
> HttpClient supports {{Accept-Encoding}} out of the box, there is no need to 
> set it manually. Since this automatically adds {{deflate}} the lightweight 
> provider should mimic this too. Compression support cannot be disabled on the 
> lightweight provider thus to be consistent, it should be the same for the 
> HttpClient provider, but since the latter provider is more versatile one 
> could add {{<disableContentCompression />}} option to the {{settings.xml}} in 
> another ticket.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to