From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package: remove the trailing slash sign from the URL address
Date: Wed, 18 Sep 2013 18:51:55 +0200 [thread overview]
Message-ID: <20130918185155.0c045e28@skate> (raw)
In-Reply-To: <CAAXf6LU8GCW7vwVvoBrSeTaongix761F=DT1Tbh=qJ_3m32CMw@mail.gmail.com>
Dear Thomas De Schampheleire,
On Wed, 18 Sep 2013 17:34:12 +0200, Thomas De Schampheleire wrote:
> Could you clarify why this is desirable? Note that urls with our
> without trailing slash are not identical: the web server needs to
> properly support this. For example, the autobuild website does not
> properly do it (something very annoying ;) )
I do certainly welcome some help with Apache configuration to make the
rewrite rules behave better. I hate doing sysadmin stuff, so when it
worked more or less, I considered it good enough :)
What I currently have is:
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^/results/([a-f0-9]{3})([a-f0-9]{37})/(.*) /results/$1/$1$2/$3 [L]
this is needed because the old URLs were:
/results/<complete-hash>/
while the way it's stored (and the new URLs) are:
/results/<first three chars of hash>/<complete-hash>/
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-18 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 15:24 [Buildroot] [PATCH 1/1] package: remove the trailing slash sign from the URL address Jerzy Grzegorek
2013-09-18 15:34 ` Thomas De Schampheleire
2013-09-18 15:44 ` Jerzy Grzegorek
2013-09-18 17:56 ` Michael Rommel
2013-09-18 20:48 ` Jerzy Grzegorek
2013-09-18 22:31 ` Michael Rommel
2013-09-18 16:51 ` Thomas Petazzoni [this message]
2013-09-19 7:06 ` Thomas De Schampheleire
2013-09-19 19:43 ` Thomas Petazzoni
2013-09-18 22:48 ` Arnout Vandecappelle
2013-09-19 13:56 ` Michael Rommel
2013-09-20 6:23 ` Jerzy Grzegorek
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=20130918185155.0c045e28@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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