Hello,
we are planning to use Nginx for static websites hosting generated by Jekyll. Sites are generated and deployed directly from GIT by "not trusted" users. "Not trusted" means they are trusted enough to publish something on their websites, but not enough to allow them change Nginx config of shared webserver.
Nginx has all pros, but only one negative point: Server redirects specified in "not trusted" file in website directory (like .htaccess from Apache).
Part of the discussion has happened yet in jekyll-redirect-from issue: https://github.com/jekyll/jekyll-redirect-from/issues/49 But there is missing the voice of someone who knows well Nginx.
Jekyll-redirect-from is plugin what generates HTML files in place of origin path with <meta http-equiv=refresh content="0; url=/new/path">. This plugin is well adopted in Jekyll community, so preffered solution is to use it (inc. extend it by some feature).
Is there some possibility to configure Nginx to send 301 redirect if he find file with meta refresh?
This will be propably very slow, so is there way to cache it?
Or to add feature to jekyll-redirect-from to generate something what Nginx can parse without everhead on not-redirected paths? (like discussed in the issue)
we are planning to use Nginx for static websites hosting generated by Jekyll. Sites are generated and deployed directly from GIT by "not trusted" users. "Not trusted" means they are trusted enough to publish something on their websites, but not enough to allow them change Nginx config of shared webserver.
Nginx has all pros, but only one negative point: Server redirects specified in "not trusted" file in website directory (like .htaccess from Apache).
Part of the discussion has happened yet in jekyll-redirect-from issue: https://github.com/jekyll/jekyll-redirect-from/issues/49 But there is missing the voice of someone who knows well Nginx.
Jekyll-redirect-from is plugin what generates HTML files in place of origin path with <meta http-equiv=refresh content="0; url=/new/path">. This plugin is well adopted in Jekyll community, so preffered solution is to use it (inc. extend it by some feature).
Is there some possibility to configure Nginx to send 301 redirect if he find file with meta refresh?
This will be propably very slow, so is there way to cache it?
Or to add feature to jekyll-redirect-from to generate something what Nginx can parse without everhead on not-redirected paths? (like discussed in the issue)