On 5/2/05, Jeff Trawick <[EMAIL PROTECTED]> wrote: > On 5/2/05, Rici Lake <[EMAIL PROTECTED]> wrote: > > > > If the action is required to compensate for a browser bug, wouldn't it > > be better to leave it as an environment variable and set it with > > BrowserMatch? > > You're absolutely right. I put the blinders on to environment > variables when I saw that mod_env didn't do anything until the fixup > hook, which is too late for processing of Redirect directives. But > mod_setenvif does its work sooner and is the proper solution.
Funny. I just heard from a Japanese user with an issue with this path too, but this time with 2.0. A third-party module is generating a custom error response and specifies a Japanese codepage in the generated HTML. But it goes through this error response code and picks up the "charset=iso-8859-1" attribute. This particular situation isn't tied to a particular browser, but I'll still use the suppress-error-charset solution so that it matches 1.3. The user can use SetEnvIf with Request_URI to match all requests.
