From: Jakub Narebski <jnareb@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCHv3] gitweb: make static files accessible with PATH_INFO
Date: Wed, 28 Jan 2009 01:58:44 +0100 [thread overview]
Message-ID: <200901280158.44386.jnareb@gmail.com> (raw)
In-Reply-To: <200901280155.26399.jnareb@gmail.com>
Jakub Narebski wrote:
> On Wed, 28 Jan 2009, Giuseppe Bilotta wrote:
> > On Wed, Jan 28, 2009 at 1:14 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> > > On Tue, 27 Jan 2009, Giuseppe Bilotta wrote:
>
> > > > Of course, last time I forgot that the BASE href is supposed to be
> > > > absolute. While Opera apparently has no problem with it being relative,
> > > > other browsers such as Firefox are stricter about it.
> > >
> > > Errrr... I think you are talking about _full_ vs. _absolute_, not
> > > _absolute_ vs. _relative_, see below.
> >
> > No, I actually mean absolute vs relative in the URI sense, not in the
> > Perl/CGI sense.
> >
> > http://www.example.com/ is absolute, / is relative
>
> No, "/" is not relative, it is absolute, because it begins with '/'.
Ooops, sorry, I mistook absolute _path_ for absolute _URL_.
Nevertheless path beginning with "/" inherits only net_loc (host).
--
Jakub Narebski
Poland
prev parent reply other threads:[~2009-01-28 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 13:29 [PATCHv3] gitweb: make static files accessible with PATH_INFO Giuseppe Bilotta
2009-01-28 0:14 ` Jakub Narebski
2009-01-28 0:43 ` Giuseppe Bilotta
2009-01-28 0:55 ` Jakub Narebski
2009-01-28 0:58 ` Jakub Narebski [this message]
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=200901280158.44386.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.