caching details
spent the evening sorting out the exyus framework response to caching headers. i *thought* i had a simple system in place, but - after some testing and thinking about what the RFC2616 really means - i think i have more work to do.
i want to support both expiration and validation caching headers. that's cool, i get the picture and have simple support for each of them. but it dawned on me that i also need to consider the possibility that a client will send *more than one* caching header [Doh!]. that's when it can get dicey.
consider the list for (just) validation headers:
- If-Match
- If-None-Match
- If-Modified-Since
- If-Unmodified-Since
- If-Range
since more than one might be present, there's a precedence to deal with as well as a combination of true/false results to consider. i have the basics, but will need to sort out the details before i get it exactly right.
actually, not a bad situation. i'm learning a lot here!