W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

[HTTP/1.1] method length and 501 Not Implemented

From: Karl Dubost <karl@la-grange.net>
Date: Tue, 12 Mar 2013 19:07:47 -0400
Message-Id: <9706C908-67B6-49E5-871A-A6691F192F91@la-grange.net>
To: IETF HTTP Working Group <ietf-http-wg@w3.org>

in "3.1.1.  Request Line"
There is a strange sentence:

   HTTP does not place a pre-defined limit on the length of a request-
   line.  A server that receives a method longer than any that it
   implements SHOULD respond with a 501 (Not Implemented) status code.

a method "longer"?
The way I understand the sentence is that if the server has implemented the methods, let's say:


so 7 characters for the longest method. If the server receives a method which is 


it sends a "501 Not Implemented", but then why not for a 2 characters long method like


What was the reason for this specific requirement on the length of the method.

Karl Dubost
Received on Tuesday, 12 March 2013 23:07:53 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 1 October 2015 05:36:58 UTC