In server/core.c: ap_core_translate, the function apr_filepath_merge is called
two
different times. Most of the errors from apr_filepath_merge relate to resulting
local path values that fall outside the valid server path and make sense to
return a
403.
There is one case here that is not so
Paul J. Reder wrote:
In server/core.c: ap_core_translate, the function apr_filepath_merge is
called two
different times. Most of the errors from apr_filepath_merge relate to
resulting
local path values that fall outside the valid server path and make sense
to return a
403.
There is one
