- From: Martin Presler-Marshall <mpresler@us.ibm.com>
- Date: Wed, 7 Apr 2004 08:30:15 -0400
- To: lexhamilton@netscape.net (Alexander Hamilton)
- Cc: www-p3p-dev@w3.org, www-p3p-dev-request@w3.org
- Message-ID: <OF4DC7B4AC.5831C7F7-ON85256E6F.0043ECCD-85256E6F.0044B038@us.ibm.com>
There is a feature in HTTP called "content negotiation" which is intended to solve this. The solution is to use a single URL for the policy. Create multiple policy files on your Webserver, one for each language. Then get your Webserver to inspect the client's language preference and send back the best fit for them. How you do this varies from Webserver to Webserver. The Apache documentation for content negotiation can be found at http://httpd.apache.org/docs-2.0/content-negotiation.html -- Martin Martin Presler-Marshall - IBM WebSphere Portal Performance lexhamilton@netscape.net (Alexander Hamilton) Sent by: www-p3p-dev-request@w3.org 04/06/2004 12:23 PM To: www-p3p-dev@w3.org cc: Subject: P3P deployment in multiple languages I want to deploy P3P on our webservers, but seem to have an issue with multiple languages. Specifically, it seems that the webserver can only point to 1 P3P xml file, not one per language - meaning that country sites with multiple languages are only able to have one version across the whole site. Is this correct? Are there any work arounds for this that you know of? All help and comment appreciated. A __________________________________________________________________ Introducing the New Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp
Received on Wednesday, 7 April 2004 08:31:08 UTC