[
https://issues.apache.org/jira/browse/JENA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372351#comment-16372351
]
David Cook edited comment on JENA-1480 at 2/22/18 2:45 AM:
-----------------------------------------------------------
It is rather bizarre to me as well.
I have already changed shiro.ini to work on more than just localhost.
I just tried the "-g" option with cURL and Tomcat is still returning a 400 Bad
Request error. I guess cURL doesn't encode user-provided URLs while wget
appears to do so.
Ok trying the 3.6.0 standalone server now... and it's working. I'm getting 200
codes. The quotes aren't encoded though. It looks like Jetty might just be less
strict than Tomcat:
{code:java}
[2018-02-22 13:40:43] Fuseki INFO [3] GET
http://<IP>:<PORT>/<DB>/query?query=select%20?g%20(count%20as%20?count)%20{graph%20?g%20{?s%20?p%20?o}}%20group%20by%20?g
[2018-02-22 13:40:43] Fuseki INFO [3] GET /<DB>:: 'query' :: <none> ?
query=select%20?g%20(count%20as%20?count)%20{graph%20?g%20{?s%20?p%20?o}}%20group%20by%20?g
[2018-02-22 13:40:43] Fuseki INFO [3] Query = select ?g (count as ?count)
{graph ?g {?s ?p ?o}} group by ?g
[2018-02-22 13:40:43] Admin INFO [4] GET http://<IP>:<PORT>/$/stats/<DB>
[2018-02-22 13:40:43] Admin INFO [4] GET stats dataset /<DB>
[2018-02-22 13:40:43] Admin INFO [4] 200 OK (12 ms){code}
So I'm guessing that this may have been a problem for a long time but most
people run the standalone server rather than the WAR in Tomcat?
was (Author: dcook):
It is rather bizarre to me as well.
I have already changed shiro.ini to work on more than just localhost.
I just tried the "-g" option with cURL and Tomcat is still returning a 400 Bad
Request error. I guess cURL doesn't encode user-provided URLs while wget
appears to do so.
Ok trying the 3.6.0 standalone server now... and it's working. I'm getting 200
codes. The quotes aren't encoded though. It looks like Jetty might just be less
strict than Tomcat:
[2018-02-22 13:40:43] Fuseki INFO [3] GET
http://<IP>:<PORT>/<DB>/query?query=select%20?g%20(count(*)%20as%20?count)%20\{graph%20?g%20{?s%20?p%20?o}}%20group%20by%20?g
[2018-02-22 13:40:43] Fuseki INFO [3] GET /<DB>:: 'query' :: <none> ?
query=select%20?g%20(count(*)%20as%20?count)%20\{graph%20?g%20{?s%20?p%20?o}}%20group%20by%20?g
[2018-02-22 13:40:43] Fuseki INFO [3] Query = select ?g (count(*) as ?count)
\{graph ?g {?s ?p ?o}} group by ?g
[2018-02-22 13:40:43] Admin INFO [4] GET http://<IP>:<PORT>/$/stats/<DB>
[2018-02-22 13:40:43] Admin INFO [4] GET stats dataset /<DB>
[2018-02-22 13:40:43] Admin INFO [4] 200 OK (12 ms)
So I'm guessing that this may have been a problem for a long time but most
people run the standalone server rather than the WAR in Tomcat?
> Bad Request 400 returned when clicking "count triples in all graphs" in
> Fuseki info
> -----------------------------------------------------------------------------------
>
> Key: JENA-1480
> URL: https://issues.apache.org/jira/browse/JENA-1480
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Jena 3.7.0
> Reporter: David Cook
> Priority: Minor
> Attachments: error.html
>
>
> When I click "count triples in all graphs", the UI doesn't change and I see
> the following in the Chrome console:
> {noformat}
> GET
> <FUSEKI_URL>/query?query=select%20(count(*)%20as%20?count)%20\{?s%20?p%20?o}
> 400 (Bad Request)
> jquery-1.10.2.min.js:6
> {noformat}
> I've experienced this in Fuseki 2.6.0 when using the WAR too. I'm also using
> the "tdb:unionDefaultGraph true" configuration setting.
> I've used someone else's install of Fuseki 2.5.0 and it works for them. I
> don't think they're using "tdb:unionDefaultGraph true", and I'm not sure if
> they're using the WAR or a standalone. Since there is no Server:
> Apache-Coyote response header, I'm guessing they're using the standalone. I
> don't know if that would make a difference.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
