Rob Heittman wrote:
The main reason I've used it is to fetch content-length and make any necessary provisions (check storage space, warn user, etc.) on the client side before fetching the representation. In this case you definitely don't want the whole GET response coming at ya.
Ya, OK. I like that. That's a very good use case. I can definitely agree, though it's obviously not traditional with a web browser, but more for automated clients.
Of course, if we could rewrite the HTTP spec, pie in the sky it could be a conditional get header. I.e. If-Smaller-Than or some such thing. Or, maybe an Accept-Size header. That'd be neat. :)
Adam
