Visitar URL original
Add HTTP return code 418 by RinkAttendant6 · Pull Request #3 · php-fig/http-message-util · GitHub
Skip to content

Add HTTP return code 418 - #3

Merged
weierophinney merged 1 commit into
php-fig:masterfrom
RinkAttendant6:http-418
Feb 6, 2017
Merged

weierophinney merged 1 commit into
php-fig:masterfrom
RinkAttendant6:http-418

Conversation

@RinkAttendant6

Copy link
Copy Markdown
Contributor

Resolves #2.

@weierophinney
weierophinney merged commit 1eec95f into php-fig:master Feb 6, 2017
weierophinney added a commit that referenced this pull request Feb 6, 2017
weierophinney added a commit that referenced this pull request Feb 6, 2017
weierophinney added a commit that referenced this pull request Feb 6, 2017
@weierophinney

Copy link
Copy Markdown
Contributor

Thanks, @RinkAttendant6! Released with version 1.1.1.

@RinkAttendant6
RinkAttendant6 deleted the http-418 branch February 6, 2017 19:25
@martinmine

martinmine commented Aug 11, 2017 •

Copy link
Copy Markdown

Note that the spec @RinkAttendant6 commits is actually an aprils fools. Note the date https://tools.ietf.org/html/rfc2518 also, it quotes: "This memo provides information for the Internet community. It does not specify an Internet standard of any kind.". HTTP 418 is according to IANA unassigned: https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

@RinkAttendant6

Copy link
Copy Markdown
Contributor Author

Regarding #3 (comment)

It might be a joke by the IETF, but there are certainly sites that implement it. Besides, I doubt that a future RFC would use the status code, and if there are, another change to this library would be warranted.

@martinmine

Copy link
Copy Markdown

@RinkAttendant6 where is my HTTP BREW then? :(

@RinkAttendant6

Copy link
Copy Markdown
Contributor Author

@martinmine There's four servers that advertise support for the BREW method in their Access-Control-Allow-Method response header: https://www.shodan.io/search?query=BREW+http+access-control-allow-methods

@martinmine

Copy link
Copy Markdown

@RinkAttendant6 thnx

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

Successfully merging this pull request may close these issues.

3 participants