What you are seeing is correct behavior, DocumentRoot is an absolute
path, whether you have specified this or not. If httpd sees an incomplete
path, it is going to work out an absolute path from the ServerRoot If it
appends the default and cannot establish a full path, you will receive
the
You can set the DocumentRoot to "C:/" (note the forward slash instead of
the backslash).
You can technically set it to just "/" also if you want the drive where
HTTPD is located.
When running HTTPD on Windows, it is good practice to use forward slashes
even though backslashes work in some places.
On Fri, Mar 10, 2017 at 8:25 AM, Ishan Thakur
wrote:
> “We are setting the documentRoot as “web”(no complete absolute path). This
> works fine for all the paths.
> The paths can be direct drive(D:\). But it fails only for C drive(C:\). The
> same works fine for all
Hi All, We areusing http-2.2.31 for our application on Windows.We arerunning
our application as Local Service on Windows.
The problem description is as follows:
“We are setting the documentRoot as “web”(no complete absolute path). Thisworks
fine for all the paths.
The paths can be direct