You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Paul Hermans <pa...@proxml.be> on 2012/01/05 18:01:35 UTC
safeguarding a Fuseki sparql endpoint
Is it possible to configure Fuseki to safeguard the SPARQL endpoint against excessive usage?
If yes, are there some settings you are able to share?
Many thanks,
Paul
Re: safeguarding a Fuseki sparql endpoint
Posted by Paolo Castagna <ca...@googlemail.com>.
Hi Paul,
it is possible to configure a timeout for each SPARQL query, see Section "Service 3" [1]:
<#dataset> rdf:type tdb:DatasetTDB ;
tdb:location "DB" ;
# Query timeout on this dataset (1s, 1000 milliseconds)
ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "1000" ] ;
[...]
.
Fuseki uses Jetty, therefore, in theory, one could benefit from Jetty features
to protect against too aggressive users, such as:
- http://wiki.eclipse.org/Jetty/Reference/DoSFilter
- http://wiki.eclipse.org/Jetty/Reference/QoSFilter
Others put Fuseki behind a web server|proxy anyway and they do this sort of things elsewhere.
Paolo
[1] http://incubator.apache.org/jena/documentation/serving_data/
Paul Hermans wrote:
> Is it possible to configure Fuseki to safeguard the SPARQL endpoint against excessive usage?
> If yes, are there some settings you are able to share?
>
> Many thanks,
>
> Paul
>
>
>
>
>
>
>
>