Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package: remove the trailing slash sign from the URL address
Date: Wed, 18 Sep 2013 22:48:12 +0200	[thread overview]
Message-ID: <523A118C.8080001@trzebnica.net> (raw)
In-Reply-To: <9FA76BDE-EE31-4C40-B226-FBBBDFB35FCE@layer-7.net>


Hi Michael,


> Hi Jerzy,
>
>
> On Sep 18, 2013, at 17:44 , Jerzy Grzegorek 
> <jerzy.grzegorek at trzebnica.net <mailto:jerzy.grzegorek@trzebnica.net>> 
> 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 ;) )
>>>
>>
>> The only reason is - for BR consistency.
>>
>
> actually I would not recommend to implement that. The RFC 3986 states 
> in chapter 6.2.3: "In general, a URI that uses the generic syntax for 
> authority with an empty path should be normalised to a path of "/".
>
> It is common practise to redirect from the URL without trailing slash 
> to one with a trailing slash. So in essence, in most times when 
> the user selects a url without a trailing slash, an unnecessary  round 
> trip to the web server occurs.
>

Thanks for the clarification.

What we have now is:
about 800 package URLs without trailing slash
about 230 package URLs with a trailing slash

We have following possibilities:
*  current package URLs:
1. leave all current package URLs as they are
2. change all current package URLs for those without trailing slash
3. change all current package URLs for those with a trailing slash
4. other action (what?)
*  new package URLs:
a. add the trailing slash to all new package URLs
b. other action (what?)

What should we do : 1+a, 2+a, 3+a, 4+a, 1+b, 2+b, 3+b or 4+b ?

Regards,
Jerzy


>   Michael.
>
> -- 
> Michael Rommel, Erlangen, Germany
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130918/ab7fcdbe/attachment.html>

  reply	other threads:[~2013-09-18 20:48 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 [this message]
2013-09-18 22:31         ` Michael Rommel
2013-09-18 16:51   ` Thomas Petazzoni
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=523A118C.8080001@trzebnica.net \
    --to=jerzy.grzegorek@trzebnica.net \
    --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