[
https://issues.apache.org/jira/browse/JENA-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264891#comment-14264891
]
Andy Seaborne commented on JENA-844:
------------------------------------
The UI could POST all queries -- there is no real reason to use GET for this
setup. HTTP caching and the update process don't play well together.
> Fuseki 2 UI: Query form, doesn't (seem to) use POST for large queries
> ---------------------------------------------------------------------
>
> Key: JENA-844
> URL: https://issues.apache.org/jira/browse/JENA-844
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.0.0
> Reporter: Stuart Williams
>
> Large queries entered into the Fuseki 2 UI query form provoke and inline
> response of :
> "Sorry, that didn't work because: 'Request Entity Too Large'"
> and a server console log entry of:
> [2015-01-05 16:47:58] HttpParser WARN Header is too large >8192
> [2015-01-05 16:47:58] HttpParser WARN badMessage: 413 for
> HttpChannelOverHttp@27dd37f3{r=0,a=IDLE,uri=-}
> I can't tell, but don't think that the UI is switching over to use POST'ed
> SPARQL queries above some threshold.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
