Thwarted, so far...
I am able to make my "server" 100% P3P-compliant (NO cookie-blocking!) by installing the appropriate files in a W3C folder off the root.
HOWEVER, for a very mysterious (to me, anyway!) reason, the same fix DOESNT work in my XOOPS root directory.
The XOOPS system is somehow automatically putting a "wrapper" around the P3P XML file, but the frame content is 'munged' and un-reachable due to the addition of an extra (unwanted!) slash character...
So instead of getting my nice P3P compliancy XML file, the XOOPS site somehow serves up a useless HTML file (sans the content)
(see details below...)
Does anybody know WHAT file i can edit to change (or preferably disable!) this wrapper? I'm very puzzled about the EXTRA slash - and how the rest of the site functions perfectly with it.
Does anybody know where i can get some DOCUMENTATION on the 'guts' of this system? I dont relish having to read through 500 files to sort this out...
BTW, I tried making an HTACCESS file in the XOOPS root directory to make a P3P HTTP header, but its not working either
+++++++++++++++++++++++++++++++++++++++++++++
Results of P3P validation
Target URI:
http://likkiwalker.com/--------------------------------------------------------------------------------
Step 1: /w3c/p3p.xml Validation
URI:
http://likkiwalker.com/w3c/p3p.xmlStep 1-1: Access check
/w3c/p3p.xml can be retrieved.
Message: The content type of /w3c/p3p.xml is text/html.
Step 1-2: Syntax check
/w3c/p3p.xml is NOT an well-formed XML file
.
mismatched tag at line 9, column 2, byte 398:
The Official Likki Walker website =^