Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serve vocabulary through a SPARQL endpoint (proxied through Apache) #38

Closed
clange opened this issue Jan 30, 2015 · 3 comments
Closed

Serve vocabulary through a SPARQL endpoint (proxied through Apache) #38

clange opened this issue Jan 30, 2015 · 3 comments

Comments

@clange
Copy link
Contributor

clange commented Jan 30, 2015

… and wrap the SPARQL endpoint into port 80 by using some kind of an Apache proxy configuration (because other ports will not necessarily be open on the server that runs VoCol, for security reasons).

Here's how this proxy configuration works: http://stackoverflow.com/questions/7529324/how-to-rewrite-proxy-an-apache-uri-to-an-application-listening-on-a-specific-p. The same pattern will be applicable to making Google App Engine (for schemaorg) on port 8080 publicly available through port 80.

@clange clange changed the title Serve vocabulary through a SPARQL endpoint Serve vocabulary through a SPARQL endpoint (proxied through Apache) Feb 10, 2015
@lavdim
Copy link
Contributor

lavdim commented Feb 11, 2015

Part of making Google App Engine available through port 80 - finished

@clange
Copy link
Contributor Author

clange commented Feb 12, 2015

I.e. now also Fuseki works through the proxy? Please let me know how; today in the afternoon I can configure the demo server accordingly.

@lavdim
Copy link
Contributor

lavdim commented Dec 22, 2016

Fixed.

@lavdim lavdim closed this as completed Dec 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants