https://issues.apache.org/bugzilla/show_bug.cgi?id=39727





--- Comment #33 from Edgar Ehritt <[email protected]>  2009-05-23 05:22:29 PST ---
Hi,


I refer to https://issues.apache.org/bugzilla/show_bug.cgi?id=47253 . In
this situation imho fixing it this way is retrograde step. There is a
question I would like to ask here:

Why you do not determined a policy?

   - Etag will formed as usual.
   - Configuration tree, that handle a resource, add fourth digest part
     into Etag-values.
   - Each filter transforming contents (on-the-fly) have to add a suffix.

I imagine, each handler have a unique key (let's say mod_deflate "DE" and
mod_include "IN" etc.). Configuration tree means a string consisting of
all keys [ simple: next = etag_uint64_to_hex(next, "IN:CH:DE"); ]. So a
change of configurations will be unique in Etag as well. But sensible
configuration information should encodet twice (first time nonreversible
by including a static unique-ID of environment) to withhold clients from
it. Already configuration tree is being parsed. It means there is a small
overhead in prucedures like that.

https://svn.apache.org/viewcvs.cgi?view=rev&rev=761835 it works fine befor
change. Only you should remove all added suffixes, then check condition
requests. Befor Etag-value are comprised that way:
"%{resource_digest}"-suffix
Only check %{resource_digest}. (modules/http/http_protocol.c; function
ap_meets_conditions(); line 270)

The worse is yet to come:
I see now way to determine mod_ext_filter. Handler module should remove
all symbols form responce header line Cache-Control how make it cache
able, and maybe statically add symbols to force inability.

I'm sorry. English is not my nativ language. ;-\


With best regards from Berlin
eddi

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to