We're doing a cookie audit for a client in view of upcoming EU legislation change re their usage, and need a bit more info on the cookies used in Articulate Presenter - can anyone tell me what the
ASP.NET SessionID cookie and the UserKeyxxxxx cookie contain?
Hi, folks (take 2, as take 1 was eaten up by web gremlins)
I was doing a similar audit for http://www.leeds.ac.uk/articulate (btw, I really like the Attacat Cookie Audit Tool - http://www.attacat.co.uk/resources/cookies) when it threw up a strange cookie to me: the MochiBot. I googled it, found its website: http://www.mochibot.com/ and, because it said it's used to track Flash content, kind of jumped to the conclusion that it must be associated with the Articulate Flash resources we have on the website.
2 seconds later I realised the shoddiness of my work and remembered that nothing has ever been gained with the 'I'm too busy' password, went back, redid the audit in smaller increments to try and pinpoint the real source, and it turned out that the cookie must have come from the xspf_player which I'm using on one page to display an audio testimonial from one of our users: http://www.leeds.ac.uk/articulate/use.html
There you have it: Articulate Studio continues to be squeaky clean as usual if you ask me, and doing things slowly pays off once again :)
2 Replies
Hi, folks (take 2, as take 1 was eaten up by web gremlins)
I was doing a similar audit for http://www.leeds.ac.uk/articulate (btw, I really like the Attacat Cookie Audit Tool - http://www.attacat.co.uk/resources/cookies) when it threw up a strange cookie to me: the MochiBot. I googled it, found its website: http://www.mochibot.com/ and, because it said it's used to track Flash content, kind of jumped to the conclusion that it must be associated with the Articulate Flash resources we have on the website.
2 seconds later I realised the shoddiness of my work and remembered that nothing has ever been gained with the 'I'm too busy' password, went back, redid the audit in smaller increments to try and pinpoint the real source, and it turned out that the cookie must have come from the xspf_player which I'm using on one page to display an audio testimonial from one of our users: http://www.leeds.ac.uk/articulate/use.html
There you have it: Articulate Studio continues to be squeaky clean as usual if you ask me, and doing things slowly pays off once again :)
Take care,
Dragos :)
There we are, it's confirmed I think: the person that's written the XSPF player is using MochiBot: http://blog.lacymorrow.com/page/6/
This discussion is closed. You can start a new discussion or contact Articulate Support.