Skip to content

Conversation

dunglas
Copy link
Member

@dunglas dunglas commented Jul 16, 2016

Q A
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets n/a
License MIT
Doc PR n/a

@dunglas dunglas merged commit 5e5f477 into api-platform:master Jul 16, 2016
@dunglas dunglas deleted the errors branch July 16, 2016 14:23
And the JSON should be equal to:
"""
{
"type": "https://tools.ietf.org/html/rfc2616#section-10",
Copy link
Contributor

Choose a reason for hiding this comment

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

RFC 2616 is obsolete. See RFC 7231 instead.

Copy link
Contributor

@teohhanhui teohhanhui Jul 18, 2016

Choose a reason for hiding this comment

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

So this should be (if we use specific URIs for each status code):

    "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1"

p/s: The indentation in this section is wrong (3 spaces instead of the intended 4)

magarzon pushed a commit to magarzon/core that referenced this pull request Feb 12, 2017
Add support for the API Error format (RFC 7807) and more tests
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.

2 participants