W3C home > Mailing lists > Public > www-p3p-dev@w3.org > October 2001

Re: Case sensitivity of urls

From: Giles Hogben <giles.hogben@jrc.it>
Date: Mon, 29 Oct 2001 15:47:04 +0100
Message-ID: <005a01c16088$935192a0$162abf8b@pcdsa22>
To: "Martin Presler-Marshall" <mpresler@us.ibm.com>
Cc: "p3pdev" <www-p3p-dev@w3.org>
That is what the URL RFC says but I think this is going to create a lot of
trouble for users.
How about introducing something into the include matching syntax akin to the
regex i flag. So that you can say
E.g. <INCLUDE case-sensitive="yes"></INCLUDE>
case-sensitive could be set to "no" by default.

----- Original Message -----
From: "Martin Presler-Marshall" <mpresler@us.ibm.com>
To: "Giles Hogben" <giles.hogben@jrc.it>
Sent: Monday, October 29, 2001 2:24 PM
Subject: Re: Case sensitivity of urls


> Giles asked:
> > The problem then is that if the user types
> > www.microsoftserver.com/testPage.html
> > as the page they wish to access, and the policy reference file only
> covers
> > www.microsoftserver.com/testpage.html, then the policy will not be found
> for
> > this page.
> >
> > Is this really the behavior we want?
>      This is definitely not ideal. However, there's no general way to know
> if a server is going to treat a URL as case-sensitive or case-insensitive.
> That depends on the operating system on the server, the Webserver it's
> running, and possibly even the type of filesystem in use on the server.
> Given that URLs are supposed to be case-sensitive, I think this is the
best
> we can do.
>
>      -- Martin
>
> Martin Presler-Marshall - Program Manager, Privacy Technology
> E-mail: mpresler@us.ibm.com     AIM: jhreingold
> Phone: (919) 254-7819 (tie-line 444-7819) Fax: (919) 254-6430 (tie-line
> 444-6430)
>
Received on Monday, 29 October 2001 09:45:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 June 2010 00:12:47 GMT