Github user michael-o commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185731400
It wasn't one because we added documentation benefit to the issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user hyPiRion closed the pull request at:
https://github.com/apache/maven-wagon/pull/23
---
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 i
Github user hyPiRion commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185701951
Alright, sorry for the disturbance.
---
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
Github user michael-o commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185689164
If I were at Ivy, I would have reject the PR at all. It is silly to
workaround such isues if you can fix the root cause. What repo managers are we
talking about? I
Github user michael-o commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185688540
If I were at Ivy, I would have reject the PR at all. It is silly to
workaround such isues if you can fix the root cause. What repo managers are we
talking about? I
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. Fi
Github user michael-o commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185583171
> 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
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-h
