[
https://issues.apache.org/jira/browse/JENA-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122873#comment-14122873
]
Niels Christensen commented on JENA-770:
----------------------------------------
You are right, of course! I had made sure there was no browser caching, but had
forgotten to account for Apache. The log says HTTP status code 304:
{noformat}
"GET /fuseki/ HTTP/1.1" 304
{noformat}
so it was Apache caching the old page. I got around it by specifically
requesting
{noformat}
http://myserver.mydomain.mytopdomain/fuseki/index.html
{noformat}
which I hadn't requested from Fuseki1.
The Fuseki2 pages seem to work like a dear in my setup.
Thanks!
> Fuseki forms assume mapping to root path
> ----------------------------------------
>
> Key: JENA-770
> URL: https://issues.apache.org/jira/browse/JENA-770
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 1.1.0
> Environment: Ubuntu x86_64
> Reporter: Niels Christensen
> Priority: Minor
> Attachments: fuseki2.png
>
>
> Some of the web forms provided by Fuseki seem to assume that they live
> directly under '/' on my web server.
> I am running a defaults-only Fuseki instance. I simply symlinked the script
> "fuseki" into /etc/init.d and executed /etc/init.d/fuseki start
> In Apache, I have mapped http://myserver.mydomain.mytopdomain/fuseki to
> localhost:3030 like this:
> {noformat}
> <VirtualHost *:80>
> ProxyPreserveHost On
> ProxyRequests Off
> ProxyPass /fuseki/ http://localhost:3030/
> ProxyPassReverse /fuseki/ http://localhost:3030/
> ...
> {noformat}
> I can get to the Control Panel without problems, but when I select the "/ds"
> namespace, I am sent to a non-existing URL
> {noformat}
> http://myserver.mydomain.mytopdomain/$/datasets
> {noformat}
> When I manipulate the URL manually to get to the SPARQL query form for "/ds",
> the same problem arises once I post a SPARQL query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
