On Tue, Jul 10, 2012 at 12:00 PM, Andy Seaborne <[email protected]> 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
