This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Shared Objects"

From OWASP
Jump to: navigation, search
(New page: OWASP Code Review Guide Table of Contents__TOC__ Shared Objects are designed to store up to 100kb of data relating to a users session. They are dependant on host and domain name and s...)
 
Line 12: Line 12:
 
In the case of cleaning the browser cachc Flash sharedobjects susvive such an action.
 
In the case of cleaning the browser cachc Flash sharedobjects susvive such an action.
  
Shared objects are handler by the Flash application and not the clients web browser.
+
Shared objects are handled by the Flash application and not the clients web browser.

Revision as of 13:27, 29 January 2008

OWASP Code Review Guide Table of Contents

Shared Objects are designed to store up to 100kb of data relating to a users session. They are dependant on host and domain name and swf movie name.

They are stored in binay format and are not cross-domain by default. Shared objects are not automatically transmitted to the server unless requested by the application.

It is worth noting that they are also stored outside the web browser cache:

C:\Documents and Settings\<USER>\Application Data\Macromedia\Flash Player\#Shared Objects\<randomstring>\<domain>

In the case of cleaning the browser cachc Flash sharedobjects susvive such an action.

Shared objects are handled by the Flash application and not the clients web browser.