its just gettng wierder, and WIERDER!

it seems that "about:blank" is some kind of "browser artifact" thats generated somehow from the redirect that points the domain name at the XOOPS root folder.

If i surf 'directly' to the XOOPS folder (in this case, via http://rockandroller.net/xoops/html/) then there is NO cookie blocking at all, and its all "GREEN LIGHTS" with regards to the XOOPS site being 100% "P3P compliant".

But getting there via the forwarded domain name still sticks me with the unknown (and decidedly non-P3P-compliant!) "about:blank". EVERY other element in the page gets a green light!


So now im pretty STUCK, i think...

It seems I somehow need to get a P3P meta-tag into the "Headers" section of the 'main frame', which comes out DIFFERENT when i reach it via domain name forwarding!

...because right now its not giving me much:

(page source for "likkiwalker.ru")



Does anybody know where i can EDIT this? Thats not even showing the proper keywords and description tags - I have different ones entered through the administration interface (which sadly doesnt allow us to add our OWN meta-tags)

(X)OOPS!!!

i'm learning as i go along here... i forgot that i had CLOAKING enabled on the redirects! I'm gonna turn that OFF, and i guess i will get the 'system' headers back again!

(I'd really prefer to have the domain cloaking WORKING, but i guess you cant have everything...)

In about 24 hours i should see if that has any helpful effect! the 'uncloaked" URL ( http://rockandroller.net/xoops/html/ ) does have the desireable HEADERS now... I just figured out that i had to switch "update themes on" temporarily in the system configuration (I edited the main theme HTML file where i found a lot of headers...)

is now showing up in the headers, and it seems to be doing the trick (preventing IE6 from blocking cookies!) when using the uncloaked URL

I'm kind of wondering about the "/" (escape character?) in front of that closing angle bracket, though - its present in all the standard XOOPS meta-tags on that page, so i thought i had better copy it...


anyway it SEEMS to be working

followup: i've confirmed its definitely a "work-around": disable domain cloaking, and the 'about:blank' goes away - permitting my P3P-compliance mechanism to function properly.

Result - NO BLOCKED COOKIES in IE6!

For the benefit of anyone else who suffers from cookie-blocking problems, here's how I fixed it:

1) created a folder off the XOOPS root called /w3c/

2) created a P3P policy file (policy1.xml) and a standard P3P referral file (p3p.xml) plus an HTML (human-readable) version of the P3P policy (p3p.html) and uploaded all of them to /w3c/ folder

(the files were created with free IBM P3P tool, (http://www.alphaworks.ibm.com/tech/p3peditor) and tested using the online P3P compliance verification tool at http://www.w3.org/P3P/validator.html )

3) edited Theme.html (in XOOPS theme folder) to add an HTML 'P3P policyref' header. (see posts above...)

More info about P3P can be found HERE: http://www.w3.org/P3P/details.html

Sorry. Out of my league now.

You might have to go to the next tier...which might involve paid support...

Guys at http://www.inboxsolutions.net are great.