Another way to get HTTPS is using a reverse proxy in front of the
server. Such reverse proxy setups are also good if the server is facing
the public internet - they can defend (usually accidental) DOS traffic.
On 16/11/2021 13:58, Vladimir Shestakov wrote:
The Jetty configuration file for the server has nothing Jena-specific
about. Any advice (StackOverflow?!) applies.
The main difference in method of Jetty run. When I run Jetty from command
line, I can pass parameters to it by arguments in command line (as I
understand). But Fuseki run Jetty by calling some method in program code,
so it is unclear how to pass additional parameters to Jetty in this case.
The <Property> are tags in the XML file.
I mean properties defined in such tags. For example jetty.base in <Property
name="jetty.base" default="." />.
For <Property>, Fuseki isn't using jetty's full start.jar sequence.
If you need more control, then it might be better to launch Fuseki from
Java so the Java can do the environment beyond Java System properties
(environment variable JVM_ARGS) and environment variables.
For base,
Fuseki Main has --base and Fuseki Webapp has environment FUSEKI_BASE.
Andy
Andy, thank you for your answer in any case.
Vladimir
