Re: Last-Modified in chunked footer

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Phillip Hallam-Baker: "RE: Globally unique e-tags, if-match on content-ID, etc."
• Previous message: Larry Masinter: "Globally unique e-tags, if-match on content-ID, etc."
• Maybe in reply to: rlgray@raleigh.ibm.com: "Last-Modified in chunked footer"
• Next in thread: Ben Laurie: "Re: Last-Modified in chunked footer"

I like Jeff's proposal, even though it's a significant broadening
of the requirements for HTTP/1.1 recipients (both clients & servers)
to deal with header-fields in a chunked trailer, since I think
it goes a long way toward making HTTP more useful with dynamically
generated content.

> In some cases, however (such as an indefinitely long server push),
> it is actually impossible to buffer the entire response at any
> point.  In such cases, one clearly needs to put the headers
> before the content!  This would seem to preclude the use of
> Content-MD5 (and some forms of Digest Authentication?) in these
> cases.

I think that "indefinitely long server push" should be explicitly
disallowed. What's a robot to do, for example? I suppose this
is a different topic.

Larry

-- 
http://www.parc.xerox.com/masinter

• Next message: Phillip Hallam-Baker: "RE: Globally unique e-tags, if-match on content-ID, etc."
• Previous message: Larry Masinter: "Globally unique e-tags, if-match on content-ID, etc."
• Maybe in reply to: rlgray@raleigh.ibm.com: "Last-Modified in chunked footer"
• Next in thread: Ben Laurie: "Re: Last-Modified in chunked footer"