Mailinglist Archive: opensuse-project (252 mails)

< Previous Next >
Re: [opensuse-project] Leap 42.1 - consistent naming
On Sun, 2015-07-26 at 08:37 -0700, PatrickD Garvey wrote:
On Sat, Jul 25, 2015 at 11:51 PM, Dimstar / Dominique Leuenberger
<dimstar@xxxxxxxxxxxx> wrote:
On Sat, 2015-07-25 at 15:55 -0700, PatrickD Garvey wrote:

Now help me understand why (note the
of a trailing /)
redirects to (with /)
but (without)

42.1-Milesteon1 is an actual existing directory on the server - so
web server can 'enter' the directory and your browser correctly
reflects this with the added /

42.1 OTOH is only a server based redirect (and does not exist as a
directory on the server). And the rule HAS to be to match 42.1$ ($
being 'end of line') as otherwise there would be strange redirects
happening for everything with 42.1 in it.

In essence: the structure on the server is setup for zypper / yast
main consumers... and for those usecases it works. For a human,
are some special cases to consider (like adding the / ).

Am i missing something about Linux directories that I didn't
from using UNIX (AIX)?

Not really - just, as noted above: only one is a directory on the
server, the other is a http server configured redirect (see for
apache's mod_rewrite for an idea)


Thank you, that answers my question completely, but it leads, of
course, to the final question, Since I don't have access to the
nor the required knowledge on how to add the additional redirect,
someone else take the initiative to add the redirect to the server?
humans like easy paths to our desired results whenever a small effort
can compensate for multiple repetitions of human frailties.

You can't do a rewrite without the trailin slash without breaking the
system badly.

In short, mod_rewrite does a pattern match / replace. The normal way
is:$ ($ indicating end of line)
rewritten to

if you now leave the $ away, you end up with being matched by
the pattern, and being rewritten as, and
so on and so forth..

I guess you understand this won't work very well :) (it CAN be worked
arund with more complexity, but that generally leads to a new can of
worms, causing much more debug work and more random errors).

(there are more such cases in the setup, like e.g: is 404, whereas redirects properly to
the Tumbleweed update channel.

The added complexity sort of does not weigh up the minimal gain

Dimstar / Dominique Leuenberger <dimstar@xxxxxxxxxxxx>
< Previous Next >
Follow Ups