I checked more carefully (should have done that before replying) and it seems that Fuseki 2 also offers the `--jetty-config` flag for using a Jetty configuration that supports HTTPS:
--jetty-config=FILE Set up the server (not services) with a Jetty XML file --- A. Soroka The University of Virginia Library On Aug 18, 2015, at 10:34 AM, aj...@virginia.edu <aj...@email.virginia.edu> wrote: > Are you deploying Fuseki to your own servlet container (e.g. Tomcat or Jetty) > or using the server included with Fuseki and is it Fuskei 1 or 2? > > If the former, you will need to supply configuration specific to that > container. If the latter and it is Fuseki 1, there is a Stack Overflow answer > for it: > > https://stackoverflow.com/questions/28310045/enable-https-ssl-on-fuseki-server > > but the links seems to be dead. The idea is to supply your own Jetty > configuration (Jetty is the servlet container that the Fuseki command uses). > For Fuseki 2, I think it is still under development? You could use a reverse > proxy in front of Fuseki, in that case. > > --- > A. Soroka > The University of Virginia Library > > On Aug 17, 2015, at 7:07 PM, Jason Levitt <slimands...@gmail.com> wrote: > >> Sorry if this is a FAQ, but I'm wondering if there are >> any guidelines online to setting up >> Fuseki for HTTPS access? >> >> Jason >
