Re: Case sensitivity of urls

But since so many people run NT or 2000, what can we do about this problem
within P3P - in testing our agent, I already found it an irritating problem
when it was set to the correct (case sensitive) behavior.
----- Original Message -----
From: "David Grant" <David_Grant@assertahome.com>
To: "Giles Hogben" <giles.hogben@jrc.it>
Sent: Monday, October 29, 2001 2:10 PM
Subject: RE: Case sensitivity of urls


> Hi Giles,
>
> Sorry, I didn't see your point before (not sure why though, after looking
> back!) but I agree that it is extremly valid.  URLs after the host and
port
> are supposed to be case-sensitive, so it seems like it is a problem that
> Microsoft need to address.
>
> Best wishes,
>
> David Grant
>
> -----Original Message-----
> From: Giles Hogben [mailto:giles.hogben@jrc.it]
> Sent: Monday, October 29, 2001 12:44 PM
> To: David Grant
> Subject: Re: Case sensitivity of urls
>
>
> But the problem is that MS servers are case-insensitive, so to write
> different policy references does not help.
> The problem 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.
> To make an include for every possible wrong case e.g. testPage.html,
> TestPage.html, TEstpage.html etc. . .
> is not feasible.
>
> > Hi Giles,
> >
> > This isn't a P3P question. The form of the URI (i.e. whether or not it
is
> > case sensitive) is covered by RFC 2396
> > (http://www.ietf.org/rfc/rfc2396.txt).  P3P interprets the URL based on
> this
> > document.  If you're on a MS server, you will have to write different
> > policies references for files with different cases.
> >
> > Thanks,
> >
> > David
> >
> > -----Original Message-----
> > From: Giles Hogben [mailto:giles.hogben@jrc.it]
> > Sent: Monday, October 29, 2001 11:24 AM
> > To: p3pdev
> > Subject: Case sensitivity of urls
> >
> >
> > We have come across a problem in our testing relating to the INCLUDE and
> > EXCLUDE urls in policy reference files:
> > The question is, should the urls contained in these be matched case
> > insensitive or case sensitive.
> > There seem to be problems associated with both alternatives:
> >
> > 1. If you require case sensitivity, then if the user accesses a
Microsoft
> > based server with the wrong case, the policy will not be found.
> > For example if I try to access www.microsoftserver.com/testPage.html
> > which is actually at www.microsoftserver.com/testpage.html
> > And my policyreference file contains <INCLUDE>/testpage.html</INCLUDE>
> > 2. If you do not require case sensitivity, then on a Unix based server,
> > there could conceivably be different policies applying to files which
> differ
> > only by case for example
> >
> > <INCLUDE>/testpage.html</INCLUDE>
> > <EXCLUDE>/testPage.html</EXCLUDE>
> >
> > What is the policy on this?
> >
> > Thanks
> >
> > Giles Hogben

Received on Monday, 29 October 2001 08:44:02 UTC