> and needs some explaining why we put open endpoints on the web without great
> restrictions
I've always been puzzled by this as well. You never see a publicly reachable
PostgreSQL or MariaDB servers, or any other database. There is always a layer
in between which defines a list of possible
It's good to see people using sparql one way or another. It's still an
unusual thing in the wild and needs some explaining why we put open
endpoints on the web without great restrictions. But since this one is
intended to be a sandbox to play with and learn I take indeed a positive
view on this
I think Laura's option is the best/easiest one, and good on you for the
positive point-of-view on these spams Marco! :D
Bruno
From: Marco Neumann
To: users@jena.apache.org
Sent: Wednesday, 19 December 2018 8:58 AM
Subject: Re: blocking IP to prevent malicious sparql queries
Thank
Thank you Laura,
I was hoping for a quick fix and something along the lines of a fuseki
blacklist filter in the shiro.ini
but yes the reverse proxy is probably a more sensible approach at this
point.
In any event good to see sparql spam like this here, it means that the
Semantic Web has most
While I think the correct answer is YES (perhaps by implementing a custom
filter), I guess the answer is going to be "use a reverse proxy".
Sent: Tuesday, December 18, 2018 at 6:16 PM
From: "Marco Neumann"
To: users@jena.apache.org
Subject: blocking IP to prevent malicious sparql queries
is it possible to block indiviual IPs with the shiro.ini?
We receive a number of malicious sparql queries from an IP in France
(193.52.210.70) today
that continuously issues the following SPARQL query:
SELECT ?r (count(*) AS ?count)
WHERE{ ?x ?r ?s
{ SELECT ?s WHERE
{ ?s a ?o }
OFFSET
