You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Adrian Gschwend <ml...@netlabs.org> on 2013/09/02 21:06:42 UTC

Restricting Fuseki to localhost

Hi group,

According to the Fuseki documentation there is a --host argument for
restricting it to some IPs:

https://jena.apache.org/documentation/serving_data/index.html#running-a-fuseki-server

but:

./fuseki-server --config=fuseki-persistent.ttl --host=127.0.0.1
Unknown argument: host

--port seems to work.

Version: Fuseki 0.2.7 2013-05-11T22:05:51+0100

Do I miss something here?

thanks

Adrian




Re: Restricting Fuseki to localhost

Posted by Adrian Gschwend <ml...@netlabs.org>.
On 02.09.13 21:12, Rob Vesse wrote:

Hi Rob,

> It's a known bug - JENA-499
> (https://issues.apache.org/jira/browse/JENA-499)

thanks for the pointer

> The --host argument is not actually supported in past versions of Fuseki
> 
> The fix which is available in the dev snapshots (1.0.0-SNAPSHOT) adds a
> --localhost argument to do this instead.

ok that will do for the moment. Any ETA for 0.2.8?

Andy asks about use-cases to bind to other IPs. While it's not very
common I did have this several times in the past when I had more than
one IP available on a host and I want to restrict the daemon to one
specific IP. Most people will probably never see that but if you have
more complex network setups it is handy.

I would call it --listen though as it's an option to what interface you
listen to.

Regarding IPv6, I'm not sure what is to blame. On my Mac I have
localhost defined in /etc/hosts for both IPv4 and Ipv6. ping resolves
127.0.0.1 while ping6 resolves to ::1.

dig/nslookup/host will not return any of these as they *always* bypass
the hosts file (by design). For that reason some network administrators
return 127.0.0.1 as an A-record for "localhost" in the local domain
which is IMHO plain wrong.

> The documentation has been corrected behind the scenes but the ASF CMS
> does not let us selectively publish parts of the website so the correction
> won't appear on the main site until we are ready to publish it.

ok

regards

Adrian

Re: Restricting Fuseki to localhost

Posted by Rob Vesse <rv...@yarcdata.com>.
It's a known bug - JENA-499
(https://issues.apache.org/jira/browse/JENA-499)

The --host argument is not actually supported in past versions of Fuseki

The fix which is available in the dev snapshots (1.0.0-SNAPSHOT) adds a
--localhost argument to do this instead.

The documentation has been corrected behind the scenes but the ASF CMS
does not let us selectively publish parts of the website so the correction
won't appear on the main site until we are ready to publish it.

Rob



On 9/2/13 12:06 PM, "Adrian Gschwend" <ml...@netlabs.org> wrote:

>Hi group,
>
>According to the Fuseki documentation there is a --host argument for
>restricting it to some IPs:
>
>https://jena.apache.org/documentation/serving_data/index.html#running-a-fu
>seki-server
>
>but:
>
>./fuseki-server --config=fuseki-persistent.ttl --host=127.0.0.1
>Unknown argument: host
>
>--port seems to work.
>
>Version: Fuseki 0.2.7 2013-05-11T22:05:51+0100
>
>Do I miss something here?
>
>thanks
>
>Adrian
>
>
>