Re: comments on draft-ietf-http-ext-mandatory-00.txt

From: Koen Holtman (koen@win.tue.nl)
Date: Wed, Apr 22 1998

Next message: Yaron Goland: "RE: "end-to-end" headers in HTTP/1.1 [was Re: Mandatory]"
Previous message: Henrik Frystyk Nielsen: "Updated Issues list for Mandatory spec"
In reply to: Henrik Frystyk Nielsen: "Re: comments on draft-ietf-http-ext-mandatory-00.txt"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Other mail archives: [this mailing list] [other W3C mailing lists]
Mail actions: [ respond to this message ] [ mail a new topic ]

From: koen@win.tue.nl (Koen Holtman)
Message-Id: <199804221617.SAA03649@wsooti20.win.tue.nl>
To: frystyk@w3.org (Henrik Frystyk Nielsen)
Date: Wed, 22 Apr 1998 18:17:27 +0200 (MET DST)
Cc: koen@win.tue.nl, ietf-http-ext@w3.org
Subject: Re: comments on draft-ietf-http-ext-mandatory-00.txt

Henrik Frystyk Nielsen:
>
>At 20:28 3/26/98 +0100, Koen Holtman wrote:
>
>>I just realised that you also may want to forbid man: headers in 304
>>responses altogether as they may overwrite an already-existing man
>>header in the cached entry.
>
>But 304 already SHOULD NOT contain any new header fields - exactly for the
>sake of consistency. Why is this different for Man than for any other header?

Hmm, I think you are right.  Protocol extensions would be free to
ignore the SHOULD NOT though, so maybe an extra word of warning is in
order.

>
>Henrik

Koen.

Next message: Yaron Goland: "RE: "end-to-end" headers in HTTP/1.1 [was Re: Mandatory]"
Previous message: Henrik Frystyk Nielsen: "Updated Issues list for Mandatory spec"
In reply to: Henrik Frystyk Nielsen: "Re: comments on draft-ietf-http-ext-mandatory-00.txt"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Other mail archives: [this mailing list] [other W3C mailing lists]
Mail actions: [ respond to this message ] [ mail a new topic ]