Search the web
Sign In
New User? Sign Up
http-compliance · discussion about HTTP compliance testing and tests
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Real people. Real stories. See how Yahoo! Groups impacts members worldwide.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
HTTP/1.1 Conditional GET   Message List  
Reply | Forward Message #103 of 117 |
Hi,

I'm writing a minimal HTTP/1.1 origin server and I'm striving for
conditional compliance.

I have a couple of newbie questions about whether Conditional GET
(and Partial GET) are required or merely recommended.

5.1.1 of RFC 2616 says:

"...if the above methods are implemented, they MUST be implemented
with the same semantics as those specified in section 9."

While 9.3 says:

"The semantics of the GET method change to a "conditional GET" if the
request message includes an If-Modified-Since, If-Unmodified-Since,
If-Match, If-None-Match, or If-Range header field. A conditional GET
method requests that the entity be transferred only under the
circumstances described by the conditional header field(s)."

This implies to me that HTTP/1.1 origin servers MUST implement
Conditional GET.

However, 3.3.1 states:

"HTTP/1.1 clients and servers that parse the date value MUST accept
all three formats..."

This implies to me that there can be HTTP/1.1 origin servers that do
not parse dates, and, since parsing dates is required for Conditional
GET, implies that they do not support Conditional GET.

Similarly for Partial GET, 9.3 says:

"The semantics of the GET method change to a "partial GET" if the
request message includes a Range header field."

Whereas 14.35.2 says:

"A server MAY ignore the Range header."

At the moment I figure I've misinterpreted "the above methods" in
5.1.1 to mean all methods, when it really means all methods except
GET and HEAD - but I'd like confirmation on this.

Also - if Conditional GET and Partial GET are indeed optional, what
is the most graceful way to handle these requests: just ignore the
If-Match, Range, etc. headers and respond as if it were a plain GET?

Thanks in advance,
-Chris






Mon Jun 2, 2003 11:11 pm

chris_pressey
Offline Offline
Send Email Send Email

Forward
Message #103 of 117 |
Expand Messages Author Sort by Date

Hi, I'm writing a minimal HTTP/1.1 origin server and I'm striving for conditional compliance. I have a couple of newbie questions about whether Conditional GET...
chris_pressey
Offline Send Email
Jun 3, 2003
2:10 am

... There is no clear/single MUST that says "the server MUST support a conditional or partial GET", I think. However, you may still get a practical answer to...
Alex Rousskov
rousskov@...
Send Email
Jun 3, 2003
4:58 am

... at ... must ... Thanks for your reply. Two of my primary design goals are conditional compliance and simplicity, so I'd like to be able to reduce this...
chris_pressey
Offline Send Email
Jun 4, 2003
9:34 pm

... Except for If-Match: * ... Except for If-None-Match: * especially for non-GET/HEAD methods. ... In general, your server may be serving content that was...
Alex Rousskov
rousskov@...
Send Email
Jun 4, 2003
10:33 pm

... Thanks for all the pointers. I'll make sure to include your name in the credits under "compliancy help". :) -Chris...
chris_pressey
Offline Send Email
Jun 28, 2003
6:53 pm

Hello again, ... Well, it took me a little longer than days :) (Actually, I just hadn't had time to work on it over the summer.) I think I have come up with an...
Chris Pressey
chris_pressey
Offline Send Email
Oct 1, 2003
5:25 am

... if If-Unmodified-Since is present respond with 412 Precondition Failed ... ...in other words, pessimistically assume the resource has changed. -Chris ...
Chris Pressey
chris_pressey
Offline Send Email
Oct 2, 2003
4:19 am
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help