2012/9/1 Michał Piotrowski <mkkp...@gmail.com>: > Hi, > > While comparing Symfony2 and FLOW3 Response classes I noticed that > FLOW3 supports 509 status code and Symfony don't. I checked > http://en.wikipedia.org/wiki/List_of_HTTP_status_codes - there are > many unsupported status codes that are not covered in any RFC's, but > are used by web servers and proxies. Is there a requirement to support > only status codes from RFC's? >
425 => 'Reserved for WebDAV advanced collections expired proposal', // RFC2817 Should it be "425 => 'Unordered Collection', // RFC2817" ? https://tools.ietf.org/html/draft-ietf-webdav-collection-protocol-04#section-7.2 506 => 'Variant Also Negotiates (Experimental)', // RFC2295 Should it be "506 => 'Variant Also Negotiates', // RFC2295"? http://www.ietf.org/rfc/rfc2295.txt -- Best regards, Michal http://eventhorizon.pl/ https://getactive.pl/ -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
