Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

On Wed, Feb 13, 2013 at 11:31 AM, Marc Paré <> wrote:
Le 2013-02-12 16:18, a écrit :

And of course, there is always the question of some other rogue pages
referencing to "developers-2". We (I) have been caught before with renaming
a page and then hearing people complaints of broken links.

I don't have access to the backend, so I'm just guessing here, but my
understanding is that one page is redirected to the other using HTTP
status code 301 "Moved Permanently".

qubit@loopbackoffice:~/scratch/itch$ wget
--2013-02-13 13:27:23--
Resolving (
Connecting to
(||:80... connected.
HTTP request sent, awaiting response... 301 OK
Location: /developers-2/ [following]

My suggestion was that we use the simpler name as the canonical one by
switching the order of redirects. If executed properly, I do not
believe this would not break any links. (Perhaps a more interesting
question is why we used 301 instead of 302 or 307, as the name
"developers-2" sounds like a re-write or test/addendum page, but I
digress outside the scope of this bug... :-).

In any case, a minor issue. If it's easy for the IT team to fix,
please do so. If there are various impediments to a quick resolution,
please make a note and punt long :-)


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.