Skip to content

Conversation

@matthewvalimaki
Copy link

The request content-type for Exec Start needs to be "application/json" and while the Docker API does check content-type for Exec Create it was not checked for Exec Start. Using invalid content-type would lead to 500 error without explanation. The proposed change adds this missing check and explanation if invalid content-type is used.

@GordonTheTurtle GordonTheTurtle added status/0-triage dco/no Automatically set by a bot when one of the commits lacks proper signature labels Sep 18, 2015
Signed-off-by: Matthew Valimaki <matthew.valimaki@gmail.com>
@GordonTheTurtle GordonTheTurtle removed the dco/no Automatically set by a bot when one of the commits lacks proper signature label Sep 18, 2015
Signed-off-by: Matthew Valimaki <matthew.valimaki@gmail.com>
@cpuguy83
Copy link
Member

All the exec tests are failing with this.

Signed-off-by: Matthew Valimaki <matthew.valimaki@gmail.com>
Signed-off-by: Matthew Valimaki <matthew.valimaki@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This header is added in cli.call by default.

@cpuguy83
Copy link
Member

cpuguy83 commented Oct 1, 2015

Any news here? also this will need a rebase.

@calavera
Copy link
Contributor

I'm going to close this since it looks like there is no movement here. I added the check in #17125 that should fix this problem.

@calavera calavera closed this Oct 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants