This project is archived and is in readonly mode.
Teapot HTTP Status Code Missing
I'm attempting to make a service-orientated, consumer driven, web 2.0 coffee service provider called "iCoffeeZ". This product is a enterprise ready solution for delivering coffee services to the end user whilst running in the Cloud.
I found that Rails doesn't have a symbol for the HTTP status code 418 (I'm a Teapot) as defined in RFC2324 (Section 2.3.2). Thus my service has trying to send "alcohol-type" headers to incompatible machines.
The attached patch includes this status code so that I may continue to develop iCoffeeZ with full HTTP compliance. Thank you very much.
Chris
-
Jeremy KemperScalable! But it needs test coverage.
-
Chris LloydThough my knowledge is mainly limited to the coffee services problem domain, I believe that this change is tested in "controller/render_test/test_head_with_symbolic_status".
Let me assure you though, I understand your need to provide a high quality deliverable and therefore have provided a seperate test.
Many thanks.
-
-
Dave Newman
+1 Also could you add support for the BREW method, as POST is deprecated for modern coffee pots.
-
MislavCOULD THIS PATCH PLS BE APPLIED? in my company we want to switch from non-scalable HTTP to superior HTCPCP and this obvious lack of proper 418 response in Rails has been holding us back for years
-
Andrew Skegg
I think this is a great addition to the framework, but we must ensure backwards compatibility - especially with rfc1149 (which still does not have any test coverage).
-
CancelProfileIsBroken
- State changed from new to wontfix
OK, yeah, I'll be the jerk to close this. Was funny for a few months but we're trying to clean up the patch queue in advance of 2.3 release.