>Number: 4197 >Category: general >Synopsis: FYI - inodes in etags will not be the same in _replicated_ >content. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Apr 5 17:10:01 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3 >Environment: n/a >Description: I attended WCW'99, http://www.ircache.net/Cache/Workshop99/, last week. During which, Craig Willis, http://www.cs.wpi.edu/~cew/, gave a presentation, http://www.ircache.net/Cache/Workshop99/Papers/wills-abstract.html, on the cachability of web resources.
He mentioned that _identical_ resources which are replicated on more than one server will have different etags, because a resource's inode is used to calculate its etag. This will be a problem when these servers sit behing a reverse proxy. Not sure how much of a problem though. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
