[
https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708963#comment-16708963
]
Michael Osipov commented on WAGON-541:
--------------------------------------
The reason phrase handling has been removed altogether.
Looking at your sample screenshots doesn't reveal any beneficial information,
how does "Internal Error Occured" and two UUIDs add more value that the 400
itself. Infact Those two UUIDs should rather be response headers or part of the
body. Citing from RFC 7230, chapter 3.1.2: "The reason-phrase element exists
for the sole purpose of providing a textual description associated with the
numeric status code, mostly out of deference to earlier Internet application
protocols that were more frequently used with interactive text clients.". I
fail to see the textucal representation of the status code here.
> 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, MvnCmdLineV339V2.PNG,
> MvnCmdLineV360.PNG, MvnCmdLineV360V2.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)
