[
https://issues.apache.org/jira/browse/JENA-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249610#comment-13249610
]
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: https://issues.apache.org/jira/browse/JENA-218
> 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
> http://tools.ietf.org/html/draft-loreto-http-timeout-00, 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
> http://incubator.apache.org/jena/documentation/serving_data/.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
