From: normalperson at yhbt.net (Eric Wong)
Subject: trailing slash page canonicalization
Date: Sun, 15 May 2016 11:17:37 +0000 [thread overview]
Message-ID: <20160515111736.GA4599@dcvr.yhbt.net> (raw)
In-Reply-To: <CAHmME9qcMwD0eopP-+M3VkTkB=Y3+XRURY2pqgauu9n04hg1TA@mail.gmail.com>
"Jason A. Donenfeld" <Jason at zx2c4.com> wrote:
> We have another potential issue, however. git.zx2c4.com/cgit and
> git.zx2c4.com/cgit/ have the same content, yet different URLs. This
> might be looked upon unfavorably by search engines. One rectification
> is to add a meta tag. Another, and one I'd like to consider here, is
> to always add the trailing slash to pages with the same 301 trick as
> [1].
I think canonicalizing is a good idea to improve cacheability, too.
For HTML, I favor trailing slash for consideration with people
who want to mirror to a static site (e.g. with "wget -r -np").
That results in "$DOCROOT/foo/index.html" on the FS; making it
easy for common configurations of static HTTP servers to serve
for "/foo/" using the "$DOCROOT/foo/index.html" file.
Without the trailing slash, "wget -r -np" would create a
"$DOCROOT/foo" file, and it's not easy to serve the right
Content-Type with a static file server that way.
prev parent reply other threads:[~2016-05-15 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 19:44 Jason
2016-05-12 20:14 ` wub
2016-05-12 20:56 ` Jason
2016-05-15 11:17 ` normalperson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160515111736.GA4599@dcvr.yhbt.net \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).