ISSUE-105: What information should be communicated about client state? [Techniques] from Web Security Context Working Group Issue Tracker on 2007-08-19 (public-wsc-wg@w3.org from August 2007)

From: Web Security Context Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Sun, 19 Aug 2007 16:31:57 +0000 (GMT)
To: public-wsc-wg@w3.org
Message-Id: <20070819163157.3A6496B644@kent.w3.org>

ISSUE-105: What information should be communicated about client state? [Techniques]

http://www.w3.org/2006/WSC/track/issues/

Raised by: Thomas Roessler
On product: Techniques

Whether or not the client keeps state that can be played back to the Web site is probably relevant security context information. Talking about cookie state display might be useful.

However, it is by now well-known that there are a number of mechanisms for keeping such state, including Flash, Google Gears, and Javascript/caching tricks.

Plugins and extensions can probably be dealt with by sufficiently generic language that covers them. What to do about clever caching of javascript code? Nothing at all?

Received on Sunday, 19 August 2007 16:32:06 UTC