Difference between revisions of "Shared Objects"

From OWASP
Jump to: navigation, search
m (fixed typos)
m (Review)
 
Line 2: Line 2:
  
 
Shared Objects are designed to store up to 100kb of data relating to a users session.
 
Shared Objects are designed to store up to 100kb of data relating to a users session.
They are dependent on host and domain name and swf movie name.
+
They are dependent on host and domain name and SWF movie name.
  
They are stored in binay format and are not cross-domain by default.
+
They are stored in binary format and are not cross-domain by default.
 
Shared objects are not automatically transmitted to the server unless requested by the application.
 
Shared objects are not automatically transmitted to the server unless requested by the application.
  
Line 12: Line 12:
 
In the case of cleaning the browser cache Flash sharedobjects survive such an action.
 
In the case of cleaning the browser cache Flash sharedobjects survive such an action.
  
Shared objects are handled by the Flash application and not the clients web browser.
+
Shared objects are handled by the Flash application and not the clients' web browser.

Latest revision as of 16:50, 26 August 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 dependent on host and domain name and SWF movie name.

They are stored in binary 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 cache Flash sharedobjects survive such an action.

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