session initiator / wayf question

[Mike Flynn]

I ran a fiddler trace on one of the failing accounts.  I am still digging through it all but I do see this:

Response sent 53 bytes of Cookie data:
Set-Cookie: sid=""; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/

Response sent 51 bytes of Cookie data:
Set-Cookie: JSESSIONID=536AB83DAD4CF5ADFD79B3919174CA85; Path=/

P3P Header is present:
CP="HONK"

Compact Policy token is present. A trailing 'o' means opt-out, a trailing 'i' means opt-in.

HONK
****** WARNING: Unrecognized P3P token, not defined in P3P spec. *********


Validate P3P Policies at: http://www.w3.org/P3P/validator.html
Learn more at: http://fiddler2.com/r/?p3pinfo

P3P value=HONK.  Not valid.  Would that alone cause the issue?


On Sunday, October 26, 2014 4:24 PM, Mike Flynn <shibbolethlynda at yahoo.com> wrote:
 


Thanks gents.  I'll probably be back tomorrow :)


On Sunday, October 26, 2014 1:49 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
 


On 10/26/14, 4:21 PM, "Mike Flynn" <shibbolethlynda at yahoo.com> wrote:

>logging is set pretty low on my production server - INFO only.  Would
>anything useful be in there?  I am going to try and get some test creds
>Monday and do a fiddler trace.  It's just bothersome that the day after
>we move the data center, I have 4 IDPs all reporting this exact same
>issue.

This is HTTP level stuff, nothing the SP has any visibility into in most
cases.

-- Scott


-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20141027/689552f7/attachment.html