From: wub at partyvan.eu (Juuso Lapinlampi)
Subject: trailing slash page canonicalization
Date: Thu, 12 May 2016 20:14:21 +0000 [thread overview]
Message-ID: <20160512201421.GA18035@partyvan.eu> (raw)
In-Reply-To: <CAHmME9qcMwD0eopP-+M3VkTkB=Y3+XRURY2pqgauu9n04hg1TA@mail.gmail.com>
To be honest, it feels like handling canonical URIs is what the
webserver should handle, not the CGI application unless I'm missing
something here.
A poor example but GitHub uses meta canonical URI on the repository
index, but not for issues.
Unless it's really broken and not just about SEO optimization, I would
leave the heavy lifting to the webserver.
next prev parent reply other threads:[~2016-05-12 20:14 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 [this message]
2016-05-12 20:56 ` Jason
2016-05-15 11:17 ` normalperson
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=20160512201421.GA18035@partyvan.eu \
--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).