You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Jira)" <ji...@apache.org> on 2019/12/20 11:01:00 UTC
[jira] [Updated] (JENA-1804) Fuseki filter: pass on requests that
are not matched.
[ https://issues.apache.org/jira/browse/JENA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne updated JENA-1804:
--------------------------------
Summary: Fuseki filter: pass on requests that are not matched. (was: Fuskei filter: pass on requests that are not matched.)
> Fuseki filter: pass on requests that are not matched.
> -----------------------------------------------------
>
> Key: JENA-1804
> URL: https://issues.apache.org/jira/browse/JENA-1804
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Affects Versions: Jena 3.13.1
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 3.14.0
>
>
> Taken from [users@ thread|https://lists.apache.org/thread.html/bd790ba2b02718aba46e4e80ea73a15589179c9fcd4410f4912904aa%40%3Cusers.jena.apache.org%3E].
> A request {{/dataset/name}} is routed first to "dataset" then "name" looked up in the services. If "name" is not found, a 404 is generated by the Fuseki dispatcher.
> If, instead, the Fuseki dispatcher just klevas the request alone, the name can be provided by a plain servlet or static file in conventional request routing by the container.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)