[
https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958912#comment-16958912
]
Brian E Fox commented on WAGON-541:
-----------------------------------
[~michael-o] I can't tell who or what you are referring to here?
The Reason Phrase is meant for the humans, the RFC is saying "don't write code
that tries to interpret the reason-phrase text".
Nothing being requested here is trying to do counter to the spec, on the
contrary, we're saying the HUMANS need this reason phrase, it's why it exists
in the spec. Maven should not swallow or hide this, which it didn't do until
recently.
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
