Fuseki 0.2.3 host parameter and Jetty XML file

[Michael Brunnbauer <br...@netestate.de>]

hi all

the --host= parameter of fuseki has been disabled and it seems that people
should create a Jetty XML file now and use --jetty-config=

public FusekiCmd(String...argv)
    {
...
        // Set via jetty config file.
        //add(argHost,    "--host=name or IP",    "Listen on a particular interface (e.g. localhost)") ;

However, I am not sure if I got the right default version for this file, which
is not included in the Fuseki distribution. Is this the correct one ?

http://svn.apache.org/viewvc/incubator/jena/Jena2/Fuseki/trunk/jetty-fuseki.xml?revision=1153268&view=co&pathrev=1153268

I guess there is no way to restrict updates to localhost while having SPARQL
read access from everywhere without using Apache in front of Fuseki ?

Regards,

Michael Brunnbauer

-- 
++  Michael Brunnbauer
++  netEstate GmbH
++  Geisenhausener Straße 11a
++  81379 München
++  Tel +49 89 32 19 77 80
++  Fax +49 89 32 19 77 89 
++  E-Mail brunni@netestate.de
++  http://www.netestate.de/
++
++  Sitz: München, HRB Nr.142452 (Handelsregister B München)
++  USt-IdNr. DE221033342
++  Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer
++  Prokurist: Dipl. Kfm. (Univ.) Markus Hendel

Re: Fuseki 0.2.3 host parameter and Jetty XML file

[Alex Hall <al...@revelytix.com>]

On Tue, Jul 10, 2012 at 12:00 PM, Andy Seaborne <an...@apache.org> wrote:

> On 10/07/12 11:50, Michael Brunnbauer wrote:
>
>>
>> I guess there is no way to restrict updates to localhost while having
>> SPARQL
>> read access from everywhere without using Apache in front of Fuseki ?
>>
>
> We use an Apache frontend.  It has a number of advantages for our usage so
> I haven't tried special Jetty setups much.
>
> There is (probably) a way to set up jetty to listen to two connectors
> routed to Fuseki, bind one to the localhost network adapter and only let
> that get update operations by service name.
>
> (Maybe Fuseki should provide a servlet filter for that setup)
>

FWIW, Mulgara's default configuration has a read-only service running and
an update service running on different ports, at which point it's pretty
straightforward to set up firewall rules to block remote requests on the
update port. Might be another possible approach.

-Alex

Re: Fuseki 0.2.3 host parameter and Jetty XML file

[Andy Seaborne <an...@apache.org>]

On 10/07/12 11:50, Michael Brunnbauer wrote:
>
> hi all
>
> the --host= parameter of fuseki has been disabled and it seems that people
> should create a Jetty XML file now and use --jetty-config=

Yes - it gives better control (and --host didn't do what people thought 
it did! I listens to aninterface not a specific remote machine,

>
> public FusekiCmd(String...argv)
>      {
> ...
>          // Set via jetty config file.
>          //add(argHost,    "--host=name or IP",    "Listen on a particular interface (e.g. localhost)") ;
>
> However, I am not sure if I got the right default version for this file, which
> is not included in the Fuseki distribution. Is this the correct one ?
>
> http://svn.apache.org/viewvc/incubator/jena/Jena2/Fuseki/trunk/jetty-fuseki.xml?revision=1153268&view=co&pathrev=1153268

Ye s- but treat it as a starting point, not a finished setup.  After 
all, that's why you would be using the chanageable jetty configuration 
and not the builtin default.

>
> I guess there is no way to restrict updates to localhost while having SPARQL
> read access from everywhere without using Apache in front of Fuseki ?

We use an Apache frontend.  It has a number of advantages for our usage 
so I haven't tried special Jetty setups much.

There is (probably) a way to set up jetty to listen to two connectors 
routed to Fuseki, bind one to the localhost network adapter and only let 
that get update operations by service name.

(Maybe Fuseki should provide a servlet filter for that setup)

	Andy



>
> Regards,
>
> Michael Brunnbauer
>