The caching proxy problem is solved with a Cache-Control: private response header. From the HTTP/1.1 RFC:
Indicates that all or part of the response message is intended for a single user and MUST NOT be cached by a shared cache. This allows an origin server to state that the specified parts of the response are intended for only one user and are not a valid response for requests by other users. A private (non-shared) cache MAY cache the response.
I still think that bending over backwards to create a perfectly rendered browsing experience for obsolete, minority, and buggy browsers is silly. Accessibility doesn’t require all of these CSS tricks; people with visual impairments have the ability to ensure usable fonts, even under IE/Win with pixel-specified sizing.
2 Responses to “mod_rewrite update”
Who's linking?
"CSS Font Sizing Scuffle Well, ok, it's not exactly a scuffle, but a debate I never get enough of. Fixed font ..."
"News Roundup The News Roundup for the last days, covering Movable Type, Trackback and related technologies, content syndication, web building notes ..."