Indeed, adding RAW_PATH_INFO could be a good idea, I also think that changing the PATH_INFO meaning could be worse than living with that bug. "So adding RAW_PATH_INFO, or REQUEST_URI which is currently not in the spec, to be undecoded might make more sense." Probably a bad idea to duplicate that kind of information in the environment. I don't understand what's the big deal about specifying PATH_IN