> -----Ursprüngliche Nachricht----- > Von: Nick Kew > Gesendet: Montag, 10. September 2007 16:22 > An: [email protected] > Betreff: Re: New flag for RewriteCond: novary (NV) > > > On Mon, 10 Sep 2007 13:04:19 +0200 > Plüm, Rüdiger, VF-Group <[EMAIL PROTECTED]> wrote: > > > So I propose to add the flag novary (NV) to > > RewriteCond in order to avoid adding the respective HTTP header to > > the Vary header. > > I'm in two minds about that. It's an obscure need, and it could > be inviting people to break RFC2616 and caching.
We have many such options, especially in mod_cache. This is the reason why it will be a flag and not the default value. I could try to stress out this better in the documentation that using this flag might break caching and RFC2616. > > Can you not achieve the same thing by removing the unwanted > vary entry with mod_headers' Header edit? No, because my rewrite rules process a large tree (all below /abc) and for single requests (/abc/something) the backend may decide that the response actually varies on a cookie. Another bad thing: There can be many cookie headers in a request and the response might vary only on one of them. But this is a different story. Regards Rüdiger
