incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Dutton (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-218) Fuseki should allow timeouts to be specified on a per-request basis
Date Sun, 08 Apr 2012 20:46:19 GMT


Alexander Dutton commented on JENA-218:

1/ WRT HTTP headers, one could extend the Timeout header to take both timeouts, but that's
liable to encourage people to send two timeouts to other SPARQL services. We could take note
of a Fuseki-specific header (e.g. X-Fuseki-Timeout), which will allow both to be set.

2/ Quite possibly, yes. It'd be a bit more forgiving.

3/ I standardised on seconds between the config, parameter and header as the Timeout header
is specified in seconds. Would it be confusing to have the config (internal) be milliseconds,
and the HTTP-based stuff (external) be seconds? Changing arq:queryTimeout to be in seconds
would be rather backwards-incompatible at this stage, wouldn't it? (Unless jena-dev says that
no one sets the timeout in that manner…)
> Fuseki should allow timeouts to be specified on a per-request basis
> -------------------------------------------------------------------
>                 Key: JENA-218
>                 URL:
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>    Affects Versions: Fuseki 0.2.1
>            Reporter: Alexander Dutton
>            Assignee: Andy Seaborne
>              Labels: needsdocumentation, timeout
>         Attachments: config-tdb.ttl, jena-218-1.diff
> A query endpoint might want to have different timeouts depending on whether queries are
from untrusted or trusted users, or maintenance processes. The timeout could be passed with
an X- header, a Timeout header as per,
or a query parameter, respecting the system default if none is provided. The query parameter
might be less favourable as it'd be harder to filter out for Fuseki instances behind Apache.
> There is a risk that changing the behaviour to allow timeouts to be overridden will lead
to DoSs of query endpoints open to the world to some extent. This can be mitigated by defaulting
to disallowing timeout overrides.
> I'm happy to put a patch together and document it at

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message