Permanent redirect from Github gh-pages_问答_开发者

开发者 https://www.devze.com 2023-02-17 05:48 出处：网络

I want to 开发者_开发技巧create a homepage and, for now, I think Github\'s pages features will serve my needs. However, I might want to switch to a more full-blown CMS/blog engine later on.

I want to 开发者_开发技巧create a homepage and, for now, I think Github's pages features will serve my needs. However, I might want to switch to a more full-blown CMS/blog engine later on.

Is it possible to serve a permanent redirect (HTTP 301) from Github pages in case I decide to move my homepage someplace else while preserving all the old URIs?

Best I can deduce is that Github has not yet added this. See Tekkub response from April 2010 re: adding it to the feature request list. Another message from another user in January suggests a META tag as a workaround (probably not a good solution).

Mass redirect layout technique

Individual page redirects are covered at: https://stackoverflow.com/a/36846720/895245 Actual 301s seem impossible.

If you want to mass redirect:

http://you.github.io/some/path

to:

http://new_domain.com/some/path

do as follows.

Before you move away

_layouts/default.html: the default layout

_config uses the default layout:

defaults:
  -
    scope:
      path: ''
    values:
      layout: 'default'

After you move away

create _layouts/redirect.html with an HTML redirect derived from Redirect from an HTML page along:

{% assign redir_to = site.new_domain | append: page.url %}
<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <title>Redirecting...</title>
  <link rel="canonical" href="{{ redir_to }}"/>
  <meta http-equiv="refresh" content="0;url={{ redir_to }}" />
</head>
<body>
  <h1>Redirecting...</h1>
  <a href="{{ redir_to }}">Click here if you are not redirected.<a>
  <script>location='{{ redir_to }}'</script>
</body>
</html>

_config contains:

defaults:
  -
    scope:
      path: ''
    values:
      layout: 'redirect'
new_domain: 'http://new-domain.com/some/path

replace every non-default layout with a symlink to the redirect layout. This is the only ugly part of this technique. I don't see a beautiful non-plugin solution.

For the security of their users, GitHub Pages does not support customer server configuration files such as .htaccess or .conf. However, using the Jekyll Redirect From plugin, you can automatically redirect visitors to the updated URL.

More info can be found here: https://help.github.com/articles/redirects-on-github-pages/

Yes, it is. Shortly, set up CNAME redirection by setting a custom domain on your GitHub Pages settings.

This is usually the case when you want your GitHub Pages to be served through a custom domain (let's say the user tries to access https://kamarada.github.io/, then the browser redirects to https://linuxkamarada.com/, but the pages are indeed on GitHub).

But it also works in the case when you previously had your website served by GitHub Pages and moved to another server, e.g. GitLab Pages (I imagine that could work for e.g. WordPress as well).

See this answer: the user tries to access https://kamarada.github.io/, then the browser redirects to https://linuxkamarada.com/, but the pages are actually on GitLab.