-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Include Request IDs in the Cargo output when an HTTP error occurs #8691
Copy link
Copy link
Closed
Labels
A-diagnosticsArea: Error and warning messages generated by Cargo itself.Area: Error and warning messages generated by Cargo itself.A-networkingArea: networking issues, curl, etc.Area: networking issues, curl, etc.C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Description
Metadata
Metadata
Assignees
Labels
A-diagnosticsArea: Error and warning messages generated by Cargo itself.Area: Error and warning messages generated by Cargo itself.A-networkingArea: networking issues, curl, etc.Area: networking issues, curl, etc.C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Type
Fields
Give feedbackNo fields configured for issues without a type.
Occasionally it might happen that our CDNs return the wrong data, and we need to contact support to get them fixed. It would be useful for Cargo to show either all the HTTP headers when that happen, or just the content of the
x-amz-cf-idone.cc #8647