Re: HTML File Validation - do you need it?

I think this is in your implementation of the content-servers 
related to the main server. So if you have the headers duplicated, 
this sounds like configuration issue.

What do you mean by validating on the domain itself?

Best, 

Rigo

On Thu, Feb 05, 2004 at 12:49:59PM -0500, Simeon Willbanks wrote:
> I now am having a problem with implementation.  We have three content
> servers all pointed to the same domain.  We successfully validated a p3p
> policy on all three content servers, then we validated the p3p policy on the
> domain itself. 
> 
> We also have an ad server in the mix.  It runs at port 8080.  We placed the
> same p3p policy on this server and ran the validator.  This is the message
> we received:  
> 
> HTTP headers are P3P compliant .
> Warning: Multiple P3P headers.
> P3P:CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT",
> policyref="/w3c/p3p.xml"
> P3P:CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT",
> policyref="/w3c/p3p.xml"
> 
> It appears the validator is getting double headers from our web server and
> ad server.  When the p3p policy is removed from the httpd.config file on the
> ad server, the validator does not see a p3p policy at all.  We get this
> error:
> 
> Step 2: HTTP Protocol Validation (HTTP headers )
> HTTP headers have no P3P: header.
> 
> When the double headers were in place, I loaded a few pages on our site.  IE
> blocked all cookies from the ad server, even though the validator said the
> url to the ad server was valid.  Could that be because of the presence of 2
> compact policies?  Could this be happening because of the port number?  How
> could we make only one policy appear on the ad server?  My IE settings were
> at, ???blocks cookies that do not have a compact privacy policy."
>

Received on Thursday, 19 February 2004 11:28:21 UTC