[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#351840: marked as done (apache2-doc: say more about Etags)

Your message dated Sat, 11 Nov 2006 23:05:24 +0100
with message-id <1163282724.3347.62.camel@darwin.os9.nl>
and subject line I don't think this is needed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: apache2-doc
Version: 2.0.53-5
Severity: wishlist
File: /usr/share/doc/apache2-doc/manual/mod/core.html.en
Tags: upstream

In core.html.en#fileetag say how one should look at Etags, e.g.,
ETag: "1f8019-385-411fc8c4"
The last part is probably the time in seconds since 1970 in hex. Yes
in apache1?, no in apache2? Is 1f8019 the inode in hex? Yes. Is 385 the
file size in hex? Yes in apache2, no in apache1? Anyway, say what is
going on here. And say why if the default is FileETag INode MTime Size
does it come out as INode-Size-MTime!

Also mention that if one uses the inode, one will then it will be much
harder to make identical etags on a second system, e.g., when one
wants to move a website and not have to have it be cached all over
again by ISPs. (I suppose, but I am super-novice.)

--- End Message ---
--- Begin Message --- 
Hi,

> In core.html.en#fileetag say how one should look at Etags, e.g.,
> ETag: "1f8019-385-411fc8c4"
> The last part is probably the time in seconds since 1970 in hex. Yes
> in apache1?, no in apache2? Is 1f8019 the inode in hex? Yes. Is 385 the
> file size in hex? Yes in apache2, no in apache1? Anyway, say what is
> going on here. And say why if the default is FileETag INode MTime Size
> does it come out as INode-Size-MTime!

This is because that knowledge is not necessary at all. No-one needs to
decypher an ETag; its purpose is to be unique to a given piece of
content. The documentation makes it clear how you want to define
"unique". It's better to keep the exact composition out since it doesn't
help the reader, and he who knows the parameters knows enough.

> Also mention that if one uses the inode, one will then it will be much
> harder to make identical etags on a second system, e.g., when one
> wants to move a website and not have to have it be cached all over
> again by ISPs. (I suppose, but I am super-novice.)

To anyone who knows what an inode is, this should be obvious. I'm
closing this bug. Thanks for reporting though!


Thijs

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: