[
https://issues.apache.org/jira/browse/JENA-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712368#comment-13712368
]
Alexander Dutton commented on JENA-218:
---------------------------------------
The current documentation says that one can attach a timeout to the fu:Server
using the ARQ.queryTimeout. This (setting timeouts once for all services) isn't
supported by the patch above. The patch also doesn't support setting the two
timeouts separately.
I'm going to propose dropping the suggestion of using ARQ.queryTimeout and
being able to do the following:
{code}
[] a fuseki:Server ;
fuseki:defaultTimeout (10 20) ; # Set the default timeouts to 10s and 20s
fuseki:allowTimeoutOverride true ;
fuseki:maximumTimeoutOverride (20 40) ;
fuseki:services (
<#service1>
<#service2>
) .
<#service1> a fuseki:Service ;
… ;
fuseki:defaultTimeout (5 10) ; # Override the default timeouts
fuseki:allowTimeoutOverride false .
<#service2> a fuseki:Service ;
… ;
fuseki:maximumTimeoutOverride 60 . # Override the maximum timeouts to both be
60s.
{code}
> 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
> Labels: needsdocumentation, timeout
> Attachments: config-tdb.ttl, jena-218-1.diff,
> jena-218-default-timeout.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
For more information on JIRA, see: http://www.atlassian.com/software/jira
