[ 
https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706971#comment-16706971
 ] 

Michael Osipov edited comment on WAGON-541 at 12/3/18 10:43 AM:
----------------------------------------------------------------

This happened in WAGON-529, see the 
[commit|https://github.com/apache/maven-wagon/commit/53bdf1c2f1907868787fcdb2686e99eecbcc602a].
 "Method Not Allowed" gives no further benefit over the status code. Do you 
provide custom messages which deviate from the current RFCs?

It especially happened because stuff like ""Not authorized " + reasonPhrase" 
duplicated the output, just adding clutter and the reason phrase is optional 
anyway.


was (Author: michael-o):
This happened in WAGON-529, see the 
[commit|https://github.com/apache/maven-wagon/commit/53bdf1c2f1907868787fcdb2686e99eecbcc602a].
 "Method Not Allowed" gives no further benefit over the status code. Do you 
provide custom messages which deviate from the current RFCs?

> Command Line Not Showing ReasonPhrase for Errors
> ------------------------------------------------
>
>                 Key: WAGON-541
>                 URL: https://issues.apache.org/jira/browse/WAGON-541
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>    Affects Versions: 3.2.0
>         Environment: Windows 10
>            Reporter: Aurelie Pluche
>            Priority: Minor
>         Attachments: MvnCmdLineV339.PNG, MvnCmdLineV360.PNG
>
>
> Hi,
> I work in the Azure DevOps Artifacts Packaging team at Microsoft where we 
> provide a Maven service to our customers. We often use a Reason-Phrase to 
> return information on failed requests to customers. This functionality was 
> available in previous versions of maven but seems to have disappeared in 
> Maven 3.6.0. Was this intentional?
> I have included screenshots of the cmd line response using two different 
> maven versions (3.3.9 and 3.6.0). I intentionally made a call that would 
> return a 405 error to be able to get an error response. I also used the same 
> package.
> Thanks



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

Reply via email to