[jira] [Commented] (JENA-1024) Graph Store Protocol with direct naming and GET requests causes 403.

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735403#comment-14735403 ] 

ASF subversion and git services commented on JENA-1024:
-------------------------------------------------------

Commit 7122aa6243452eecd92bc4538fa5fbfd43da97e5 in jena's branch refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=7122aa6 ]

JENA-1024: Fix acess bug and use GSP_DIRECT_NAMING flag.

> Graph Store Protocol with direct naming and GET requests causes 403.
> --------------------------------------------------------------------
>
>                 Key: JENA-1024
>                 URL: https://issues.apache.org/jira/browse/JENA-1024
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: Fuseki
>    Affects Versions: Fuseki 2.3.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>             Fix For: Fuseki 2.3.1
>
>
> The code does not handle GSP direct naming gracefully.  It returns {{403 Forbidden}} which is the wrong HTTP status code and masks proper processing.
> However, GSP direct naming should be off by default and this needs refactoring and controlled by a single flag such as {{Fuseki.GSP_DIRECT_NAMING}}.
> GSP direct naming is a confusing feature and is very fragile because the exact request URI is used to name the graph but that can be written many ways for the same name.  It also leads to confusing error messages because it is the last processing for many unrecognized requests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)