Ok, so how do we do a temporary redirect? Is this a chicken and egg problem? transparent caches wont fix this because no one uses it, no one uses it because transparent caches don't support it. signed, clueless newbie in zopeland
-----Original Message----- ---------------------SNIP ------------------ These caches will cache the first document that it gets a request for, and then serve it for all subsequent requests. This means that if a 3.0 browser grabs this page first, all subsequent 4.0 browsers will get the non stylesheet page. This is bad. There are mechanisms built into http/1.1 (netscape isn't there yet, and I don't know about Opera) that allow a server to mark a page as varying on a particular header (Vary: user-agent, or something similar), which should cause a cache to cache different copies of the object for each user-agent request that it sees. However, most caches ignore this command, since few authors do this anymnore (they learned the hard way). In general, it is best to detect css support in javascript, or design pages that work with or wothou CSS support. In other instances, if you must do a detection, get the results and then issue a redirect to the correct page (make sure it is a temporary redirect, not a permanent one, since the permanent redirect is considered a cachable object in most caches).
------------------ SNIP ---------------------