From 7179008ffaa43dc8482164ce66291864e085c9cd Mon Sep 17 00:00:00 2001 From: Jeremy Kersten Date: Fri, 23 Feb 2018 10:14:06 +0100 Subject: [PATCH] [FIX] doc: fix link to our website MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Remove wrong slash trailing Now, in V11, matching of page are done on the exact name. Previously, the error was transparent because we was using a dedicated controller that allow trailing slash. https://github.com/odoo/odoo/blob/11.0/odoo/http.py#L936 https://webmasters.googleblog.com/2010/04/to-slash-or-not-to-slash.html http://example.com/foo/ (with trailing slash, conventionally a directory) http://example.com/foo (without trailing slash, conventionally a file) Google treats each URL above separately (and equally) regardless of whether it’s a file or a directory, or it contains a trailing slash or it doesn’t contain a trailing slash. Different content on / and no-/ URLs okay for Google, often less ideal for users Special case for homepage Rest assured that for your root URL specifically, http://example.com is equivalent to http://example.com/ and can’t be redirected even if you’re Chuck Norris. --- doc/_extensions/odoo_ext/layout.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/_extensions/odoo_ext/layout.html b/doc/_extensions/odoo_ext/layout.html index cb1015d2ebe..793ed47806f 100644 --- a/doc/_extensions/odoo_ext/layout.html +++ b/doc/_extensions/odoo_ext/layout.html @@ -102,8 +102,8 @@
It's all about efficiency