homepage Welcome to WebmasterWorld Guest from
register, free tools, login, search, pro membership, help, library, announcements, recent posts, open posts,
Become a Pro Member
Visit PubCon.com
Home / Forums Index / Local / Foo
Forum Library, Charter, Moderators: incrediBILL & lawman

Foo Forum

For Adults Only: The Dirty HTTP/1.1 Spec

 9:32 pm on Aug 2, 2006 (gmt 0)


If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Unless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate.

The requested resource MUST be accessed through the proxy given by the Location field.

Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.

The client SHOULD NOT repeat the request without modifications.

The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity.

The request could not be completed due to a conflict with the current state of the resource.

Conflicts are most likely to occur in response to a PUT request.

The server refuses to accept the request without a defined Content- Length.

The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.

The expectation given in an Expect request-header field could not be met by this server

The server does not support the functionality required to fulfill the request.

Absolutely hilarious.



 10:55 pm on Aug 2, 2006 (gmt 0)

For the record, according to my log files I apparently get a lot of HEAD from AOL proxies. Wonder if that's part of their new revenue strategy?


 11:08 pm on Aug 2, 2006 (gmt 0)

The client SHOULD NOT repeat the request without modifications.

Come oooonnnn, pleeeease?

Come oooonnnn, pretty pleeeease?



 1:26 am on Aug 3, 2006 (gmt 0)

The request has been fulfilled and resulted in a new resource being created.

That new resource should be available in about 9 months :)


 5:13 am on Aug 3, 2006 (gmt 0)

RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client.

Interesting. I've always used 301 and 302 to redirect after handling a POST, and the browsers have always changed the POST request to a GET, just like I wanted them to. I guess I should start using 303.

Many pre-HTTP/1.1 user agents do not understand the 303 status.

And I guess this isn't a concern, since pre-HTTP/1.1 user agents also don't understand name virtual hosts?


 5:16 am on Aug 3, 2006 (gmt 0)

The server refuses to accept the request without a defined Content- Length.

Yes, I think the length should be established up front to avoid overflows.


 3:06 am on Aug 4, 2006 (gmt 0)

Beware when your HEAD request gets a 402 status (Payment Required)

other "adult" status codes:
403 Request Entity Too Large
414 Request-URI Too Long
411 Length Required

and the dreaded:
417 Expectation Failed

Global Options:
 top home search open messages active posts  

Home / Forums Index / Local / Foo
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Home ¦ Free Tools ¦ Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About ¦ Library ¦ Newsletter
WebmasterWorld is a Developer Shed Community owned by Jim Boykin.
© Webmaster World 1996-2014 all rights reserved