Skip to content

The description Invalid Input of 405 Responses Object is ambiguous and leads to misunderstanding #1449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
weimengxi opened this issue Dec 25, 2017 · 2 comments

Comments

@weimengxi
Copy link

weimengxi commented Dec 25, 2017

As the document says, the key of a responses object's Patterned Fields is Http Status Code .

and the document gives responses object examples like this at following part.

  "responses": {
    "405": {
      "description": "Invalid input",
      "content": {
        "application/json": {},
        "application/xml": {}
      }
    }
  }

As it defined in rfc7231 Specification , 405 indicates Method Not Allowed rather than Invalid Input .

The 405 (Method Not Allowed) status code indicates that the method
received in the request-line is known by the origin server but not
supported by the target resource.

I think we'd better follow the rfc7231 Specification 's definition

@weimengxi
Copy link
Author

weimengxi commented Dec 25, 2017

Pull Request #1450

@MikeRalphson
Copy link
Member

#1486 has been merged, many thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants