Content Handlers and Redirects
Closed this issue · 10 comments
For oslc.co for now....
We need a couple of things setup on the server:
-
The server needs to send the right content type for certain types of content for the browser to display it.
e.g. application/rdf+xml for RDF files.
e.g. file: http://oslc.co/ns/cm/cm.rdf -
Redirects need to work.
Right now I copied the site .htaccess from ns/ to a new ns/ folder on the new site. You can see it at:
https://github.com/OSLC/oslc-site-hugo/blob/master/content/ns/.htaccess
Maybe .htaccess is being ignored right now?
.htaccess is not working because it is not there! It is not being added during the deployment to oslc.co. It is not added to the oslc.git.io repository when deployed there. This would need to be fixed first.
Any update on this @hectorsanchezmx ?
.htaccess does not work in NGINX, I have added the redirects to the NGINX server block, but need to test the redirections, do we have the content on oslc.co to do that?
Let's start with this:
http://oslc.co/ns/core -> http://oslc.co/ns/core/core.rdf iff the format requested is rdf/xml
(later would be good to add text/tutle
and still force rdf/xml
reply or convert all files via Jena command line tools)
http://oslc.co/ns/core -> http://oslc.co/specifications/archive/core-2.0/ (will have to be http://oslc.co/specifications/archive/core-2.0/vocab/ in the future, but that's the problem for #194)
@hectorsanchezmx the redirect does not work yet, but the homepage is redirecting to http://oslc.co/specifications/vocabularies/
The homepage redirect is fixed now.
@hectorsanchezmx Can you please document the redirects you setup, and other nginx changes, so that someone coming in to take over will be able to understand.
From #214, we need to ensure proper redirects from HTTP to HTTPS URLs too.
I am not sure how did it happen that I unassigned @hectorsanchezmx. Maybe by accident. @hectorsanchezmx you are the right person to take care of this?
@berezovskyi no, he's no longer working at koneksys. I'll reassign the issue
all redirects are now handled in https://github.com/OSLC/oslc-site-content-negotiation