GitHub user hyPiRion opened a pull request:

    https://github.com/apache/maven-wagon/pull/23

    [WAGON-451] Accept NO CONTENT in resourceExists

    Some maven repositories may respond with 204 NO CONTENT instead of 200 OK 
when sending in HTTP HEAD requests. This throws an exception in wagon-http and 
wagon-http-lightweight.
    
    This patch makes 204 NO CONTENT responses from HTTP HEAD requests in 
wagon-http and wagon-http-lightweight return true in `resourceExists`, instead 
of throwing an exception.
    
    The patch also adds makes wagon-http-lightweight accept 304 NOT MODIFIED, 
to make it consistent with the wagon-http implementation.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hyPiRion/maven-wagon WAGON-451

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/maven-wagon/pull/23.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #23
    
----
commit 1e8c1a6b8be4c002cceda1dd2e37e4ff432f20ab
Author: Jean Niklas L'orange <[email protected]>
Date:   2016-02-17T23:42:00Z

    [WAGON-451] Accept NO CONTENT in resourceExists
    
    This patch makes 204 NO CONTENT responses from HTTP HEAD requests in
    wagon-http and wagon-http-lightweight return true in `resourceExists`,
    instead of throwing an exception.
    
    The patch also adds makes wagon-http-lightweight accept 304 NOT
    MODIFIED, to make it consistent with the wagon-http implementation.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to