[
https://issues.apache.org/jira/browse/WAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152010#comment-15152010
]
ASF GitHub Bot commented on WAGON-451:
--------------------------------------
Github user hyPiRion commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185625955
> > Some maven repositories may respond with 204 NO CONTENT instead of 200
OK when sending in HTTP HEAD requests.
>
> If so, they are violating the RFCs. File an issue against those repos.
Yeah, that was what I originally thought too, but I noticed Apache Ivy
[fixed the exact same
issue](https://github.com/apache/ant-ivy/commit/899f9fd0a9690581f33a715bb5f000397f1bafef.patch)
some years ago. So I went to look at the actual specification, and the RFC
section on [HEAD](http://tools.ietf.org/html/rfc7231#section-4.3.2) seems to
allow it, _technically_ speaking.
I agree that it does not make sense though, so feel free to close this PR
if you folks feel they are violating the RFC, and I'll bring it back to the
repo maintainers.
> wagon-http does not handle 204 as success for HEAD requests
> -----------------------------------------------------------
>
> Key: WAGON-451
> URL: https://issues.apache.org/jira/browse/WAGON-451
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http, wagon-http-lightweight
> Affects Versions: 2.10
> Environment: maven-wagon 0.2.10
> Reporter: Jean Niklas L'orange
> Priority: Minor
>
> This seems to similar to WAGON-124.
> Some maven repositories may respond with 204 no content for http HEAD
> requests. In those cases, wagon-http and wagon-http-lightweight will throw an
> exception instead of accepting it as if it was a 200 OK request.
> For a real life example of this, see
> https://github.com/technomancy/leiningen/issues/2093
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
