I have a few 301 redirects setup on github pages $ curl https://nobodywasishere....

qbasic_forever · on April 12, 2022

Is that coming back with a HTTP 200 response though and the made up HTML page? That doesn't seem right... at least, I dunno if google and such would actually index your page at the new URL vs. just thinking "huh weird looks like blog.eowyn.net is now called '301 Moved Permanently', better trash that down in the rankings".

cptskippy · on April 12, 2022

It shows up as a proper 301 when I load up the URL in Firefox. The question is, how?

MD87 · on April 12, 2022

One of the Jekyll plugins that GH Pages supports[0] is jekyll-redirect-from, which lets you put a `redirect_to` entry in a page's front matter.

[0]: https://pages.github.com/versions/

simonw · on April 13, 2022

I found this example of another repo that is using the same trick: https://github.com/kotokaze/kotokaze.github.io

    ~ % curl -i 'https://kotokaze.github.io/'
    HTTP/2 301 
    server: GitHub.com
    content-type: text/html
    permissions-policy: interest-cohort=()
    location: http://github.kotokaze.net/

nobodywasishere · on April 12, 2022

For the latter, `<meta http-equiv="refresh" content="0; URL=https://blog.eowyn.net/vhdlref" />` in the `<head>`

qbasic_forever · on April 12, 2022

Wow, nice yeah I'd love to know how github supports configuring a URL to 301 redirect!

chabad360 · on April 12, 2022

Yea, no.

A 301 (or 302) redirect means setting the status code header to 301 and providing a location header with the place to redirect to. Last I checked GitHub doesn't allow any of this, or setting any other headers (like cache-control). To work around this, I've been putting cloudflare in front of my site which lets me use page rules to set redirects if necessary.