Summary

The -d option of jwebserver command (resp. the -d option of the jdk.httpserver module main entry point) specifies the directory whose contents are to be served. This currently accepts absolute paths only but should accept relative paths as well. No compatibility issues are foreseen.

Only after we pushed this fix, we realised it may have needed a CSR. So, apologies for the backwards order of events.

Problem

Currently, jwebserver only accepts absolute path names for the -d command line option. This is unnecessarily restrictive and we would like to allow relative paths (relative to CWD) as well.

Solution

No change to jwebserver documentation is required as the requirement for an absolute path was never documented.

Specification

The -d option can now take a relative path as well as an absolute path as before. Eg.

jwebserver -d sub1/sub2 -- currently disallowed. Will be allowed

jwebserver -d /foo/bar -- currently allowed. Will still be allowed

and respectively:

java -m jdk.httpserver -d sub1/sub2 -- currently disallowed. Will be allowed

java -m jdk.httpserver -d /foo/bar -- currently allowed. Will still be allowed