form parameters
"elena" <[email protected]> Tue, 9 Jul 2002 04:25:26 -0400 (EDT)
| Newsgroups | gmane.comp.web.p3p.devel |
|---|---|
| Message-ID | <085701c22722$0742b9e0$6a1010ac@PCDASSENI> |
This is a multi-part message in MIME format.
------=_NextPart_000_084E_01C22732.C34F5700
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset="iso-8859-1"
Hi,
I've got a question on the the following paragraph, concerning the =
comparison of an action URI with parameters and the URI specified in the =
<INCLUDE> (<EXCLUDE>) node of a policy reference file:
Note that if a form is handled through use of the GET method, then the =
action URI reflects the choice of form elements selected by the user. In =
some cases, it will be possible to make use of the wildcard syntax =
allowed in policy reference files to specify different policies for =
different uses of the same form action-handler URI. Therefore, user =
agents MUST include the query-string portion of URIs when making =
comparisons with INCLUDE and EXCLUDE elements in policy reference files.
I've got a questioLet's suppose that, when clicking the submit button =
of the form, the request is the following:
http://host/URI?name=3DElena&surname=3DDasseni&city=3DMilan=20
Let's also suppose we have the following PRF at http://host/w3c/p3p.xml =
:
<META xmlns=3D"http://www.w3.org/2002/01/P3Pv1">
<POLICY-REFERENCES>
<EXPIRY max-age=3D"86400"/>
<POLICY-REF about=3Dhttp://www.website.com/policy1.xml>
<INCLUDE>/URI?*surname=3D*&name=3D*</INCLUDE>
</POLICY-REF>
<POLICY-REF about=3Dhttp://www.website.com/policy2.xml>
<INCLUDE>/URI?*name=3D*&surname=3D*&city=3D*</INCLUDE>
</POLICY-REF>
</POLICY-REFERENCES>
</META>
Both My doubts are:
1) does the parameters order count?If so, then I should say the first =
INCLUDE does not match.=20
2) if not, then both the INCLUDEs match: shall I apply the rule that the =
first POLICY-REF node matching the request URI has to be taken into =
account, and do not consider the second policy-ref, or shall I apply the =
second one,which is more precise?
Thank you very much.
-----
Elena Dasseni
Dottore in Informatica
v. Frigia, 27 =20
20126 Milano (Italia)
phone: +39-02-25771-390 =20
------=_NextPart_000_084E_01C22732.C34F5700
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> I've got a question =
on the the=20
following paragraph, concerning the comparison of an action URI with =
parameters=20
and the URI specified in the <INCLUDE> (<EXCLUDE>) node of a =
policy=20
reference file:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><EM><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Note=20
that if a form is handled through use of the </SPAN><CODE><SPAN =
lang=3DIT=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier New'; =
mso-ansi-language: IT; mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">GET</SPAN></CODE><SPAN=20
lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">=20
method, then the action URI reflects the choice of form elements =
selected by the=20
user. In some cases, it will be possible to make use of the wildcard =
syntax=20
allowed in policy reference files to specify different policies for =
different=20
uses of the same form action-handler URI. Therefore, user agents MUST =
include=20
the query-string portion of URIs when making comparisons with =
</SPAN><CODE><SPAN=20
lang=3DIT=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier New'; =
mso-ansi-language: IT; mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">INCLUDE</SPAN></CODE><SPAN=20
lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">=20
and </SPAN><CODE><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier New'; =
mso-ansi-language: IT; mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">EXCLUDE</SPAN></CODE><SPAN=20
lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">=20
elements in policy reference files.</SPAN></EM></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
size=3D2> I've got a questioLet's suppose that, when clicking the =
submit=20
button of the form, the request is the =
following:</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><A=20
href=3D"http://host/URI?name=3DElena&surname=3DDasseni&city=3DMil=
an">http://host/URI?name=3DElena&surname=3DDasseni&city=3DMilan</=
A>=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
size=3D2> Let's also suppose we have the following PRF at <A=20
href=3D"http://host/w3c/p3p.xml">http://host/w3c/p3p.xml</A>=20
:</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
size=3D2> </DIV>
<DIV><META xmlns=3D"http://www.w3.org/2002/01/P3Pv1"></DIV>
<DIV><POLICY-REFERENCES></DIV>
<DIV> <EXPIRY max-age=3D"86400"/></DIV>
<DIV> <POLICY-REF about=3D<A=20
href=3D"http://www.website.com/policy1.xml">http://www.website.com/policy=
1.xml</A>>
<DIV> =20
<INCLUDE>/URI?*surname=3D*&name=3D*</INCLUDE></DIV>
<DIV> </POLICY-REF></DIV></DIV>
<DIV> <POLICY-REF about=3D<A=20
href=3D"http://www.website.com/policy2.xml">http://www.website.com/policy=
2.xml</A>></DIV>
<DIV> =20
<INCLUDE>/URI?*name=3D*&surname=3D*&city=3D*</INCLUDE>=
;</DIV>
<DIV> </POLICY-REF></DIV>
<DIV></POLICY-REFERENCES></DIV>
<DIV></META></DIV>
<DIV></FONT></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"> <FONT=20
size=3D2>Both My doubts are:</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
size=3D2></FONT></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
size=3D2>1) does the parameters order count?If so, then I should say the =
first=20
INCLUDE does not match. </FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
size=3D2>2) if not, then both the INCLUDEs match: shall I apply the =
rule that=20
the <STRONG>first </STRONG>POLICY-REF node matching the request URI has =
to be=20
taken into account, and do not consider the second policy-ref, or shall =
I apply=20
the second one,which is more precise?</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
size=3D2></FONT></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
size=3D2>Thank you very much.</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DIT=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: IT; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></FONT><FONT=20
face=3DArial size=3D2>-----<BR>Elena Dasseni<BR>Dottore in =
Informatica<BR>v. Frigia,=20
27  =
; =20
<BR>20126 Milano (Italia)<BR>phone:=20
+39-02-25771-390 &nb=
sp;=20
</FONT></DIV></BODY></HTML>
------=_NextPart_000_084E_01C22732.C34F5700--