[
https://issues.apache.org/jira/browse/JENA-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372984#comment-14372984
]
Andy Seaborne commented on JENA-868:
------------------------------------
I think a fix is in currentRootPath() in fuseki-server.js:
{noformat}
currentRootPath: function() {
var path = window.location.pathname.replace( /\/[^/]*$/, "" );
// Relative URL
return path;
// Absolute URL
//return sprintf( "%s//%s:%s%s", window.location.protocol,
window.location.hostname, window.location.port, path );
}
{noformat}
> Fuseki2: Can't create datasets/ if accessing through different (non-3030) port
> ------------------------------------------------------------------------------
>
> Key: JENA-868
> URL: https://issues.apache.org/jira/browse/JENA-868
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.0.0
> Environment: Docker
> https://registry.hub.docker.com/u/stain/jena-fuseki/
> Reporter: Stian Soiland-Reyes
> Priority: Minor
>
> If I use docker and jena-fuseki exposing the port on something other than the
> one it is running at, e.g. with -p 3031:3030 - then in the browser at
> http://localhost:3031/ when I go to *Manage datasets* -> *Create dataset"* I
> simply get "error" because it is trying to POST to
> http://localhost:3030/datasets instead of http://localhost:3031/datasets.
> This could make it tricky to expose the Fuseki server through firewalls, web
> servers etc, as one has to change the Fuseki port to match the public port.
> All URIs should be relative and not hard-code the port. (and not the host!)
> This is using fuseki-server.jar, I have not checked what happens if I do the
> same through tomcat/WAR.
> The workaround is to always expose the same port - e.g. add the argument
> --port=3031
> docker run -p 3031:3031 stain/jena-fuseki ./fuseki-server --port=3031
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
