[jira] [Created] (MNG-6534) Command Line Not Showing ReasonPhrase for Errors

2018-11-29 Thread Aurelie Pluche (JIRA)
Aurelie Pluche created MNG-6534:
---

 Summary: Command Line Not Showing ReasonPhrase for Errors
 Key: MNG-6534
 URL: https://issues.apache.org/jira/browse/MNG-6534
 Project: Maven
  Issue Type: Bug
  Components: Command Line
Affects Versions: 3.6.0
 Environment: Windows 10
Reporter: Aurelie Pluche
 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)


[jira] [Updated] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

2018-12-03 Thread Aurelie Pluche (JIRA)


 [ 
https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aurelie Pluche updated WAGON-541:
-
Attachment: MvnCmdLineV360V2.PNG
MvnCmdLineV339V2.PNG

> 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)


[jira] [Commented] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

2018-12-03 Thread Aurelie Pluche (JIRA)


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

Aurelie Pluche commented on WAGON-541:
--

Thank you for the feedback - to answer your question: no, there is no deviation 
from the current RFCs. I see the reasoning behind removing the reason phrase 
for the 405 error code. Unfortunately, this isn't the only instance where the 
reasonPhrase isn't returned as expected.

I executed another call, this time using the Artifacts system where I know the 
reason phrase is being returned and the same thing occurs. The call 
intentionally returns a 400, which includes a reason phrase for why the call is 
failing. I used Fiddler to look at the returned headers and they are identical. 
I linked another set of images below. The first one is using maven 3.6.0 and 
the second 3.3.9. 

!MvnCmdLineV360V2.PNG!

!MvnCmdLineV339V2.PNG!

> 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)


[jira] [Commented] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

2018-12-04 Thread Aurelie Pluche (JIRA)


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

Aurelie Pluche commented on WAGON-541:
--

The answer to the initial question I asked boils down to: "The reason phrase 
handling has been removed altogether."

Thank you for your help.

> 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)


[jira] [Commented] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

2018-12-17 Thread Aurelie Pluche (JIRA)


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

Aurelie Pluche commented on WAGON-541:
--

You can go ahead and close it out.

> 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
> Fix For: waiting-for-feedback
>
> 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)