On Mon, 30 Aug 2004, Erik Abele wrote:
> I'm building some simple (but nice) statistics based on the
> weekly bug reports mailed out to the dev- and bug-list:
>
> http://www.apache.org/~erikabele/httpd/bugstats/
>
> The stats are updated every sunday just after the reports
> are mailed out. The sc
Is it metadata about the body? In many cases, a cookie is
semantically information about the "session"; it might have
nothing to do with the particular body at all.
On 29-Aug-04, at 5:57 PM, Jim Jagielski wrote:
I myself would "define" the cookie header as an entity header,
since it *is* meta data
On Sun, 29 Aug 2004, Jim Jagielski wrote:
> I myself would "define" the cookie header as an entity header,
> since it *is* meta data about the body, but I can also see
> it as a more traditional "response header" as well.
> But wouldn't adding new info about the response (either
> as a response he
I myself would "define" the cookie header as an entity header,
since it *is* meta data about the body, but I can also see
it as a more traditional "response header" as well.
But wouldn't adding new info about the response (either
as a response header or entity header) invalidate it
actually *being*
I'm building some simple (but nice) statistics based on the
weekly bug reports mailed out to the dev- and bug-list:
http://www.apache.org/~erikabele/httpd/bugstats/
The stats are updated every sunday just after the reports
are mailed out. The script which produces the PNGs is also
available at the
Trawling through a few bugs, this one looks valid to me: namely,
Set-Cookie headers should be enabled on 304 responses.
The current behaviour has a rationale, but I believe it's incorrectly
applied. Set-Cookie is a response header and does not affect a
cached entity body, so there's no reason to
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
