ASP.NET2.0 cookieless vs cookie sessions

[maboo59]

when using ASP.NET 2.0, if you set 'cookieless session = fales'
(meaning you want to use cookies), is the session information stored in
a cookie on the client machine or in the browsers memory?

Thanks
Maboo

 

[Lit]

if you want to persist the cookie then it is stored on the client machine
otherwise during actual communication it is stored in memory.
cookies can expire.

Lit

 

[Patrice]

The information needed to track the session is stored in a non permanent
cookie (not stored on disk) at least in IE (could be browser dependent).

Note all other session information are not sent accross the wire...

(not sure if the question is focused on the session id or all session
information).

 

[maboo59]

Lit,
Are yo saying that there is a setting that tells the site to write to
client machine or store in memory?

Maboo

 

[Lit]

The Expires property of the HttpCookie class makes a cookie persistent and
sets a date when a cookie will expire.
A persistent cookie enables a website to remember you on subsequent visits,
speeding up or enhancing your experience of services or functions offered.

you can also set things in web.config.
a Cookie is automatically in memory anyway.

Store what every info you want in a cookie and it is good to encrypt your
cookie also.

Lit

 

[maboo59]

good stuff Lit
thanks

The Expires property of the HttpCookie class makes a cookie persistent and
sets a date when a cookie will expire.
A persistent cookie enables a website to remember you on subsequent visits,
speeding up or enhancing your experience of services or functions offered.

you can also set things in web.config.
a Cookie is automatically in memory anyway.

Store what every info you want in a cookie and it is good to encrypt your
cookie also.

Lit

 

[maboo59]

good stuff Lit
thanks

The Expires property of the HttpCookie class makes a cookie persistent and
sets a date when a cookie will expire.
A persistent cookie enables a website to remember you on subsequent visits,
speeding up or enhancing your experience of services or functions offered.

you can also set things in web.config.
a Cookie is automatically in memory anyway.

Store what every info you want in a cookie and it is good to encrypt your
cookie also.

Lit

 

[bruce barker \(sqlwork.com\)]

when you use cookie sessions, then the session id is stored in the cookie.
the actual session data in stored on the server by the session manager.

when you use cookieless sessions, the session id is encode in the url.

http://mysite.com/myapp/<sessionid>/mypage.aspx

-- bruce (sqlwork.com)

 

[tanveer ahmad]

when we set cookies to false it means information is not stored on the
client side

 

[shiv yadav]

hi..

this is shiv.this is regarding ur question for the cookieless
session. actually when the user visits a site for the very first time, a
unique ID is created, called SessionId, that works for the user untill
he is on the site.
The Session ID is usually stored in the user's cookies. If 'cookieless
session = false' is set then it is not stored in cookies, it passes
through the URL.It is stored as part of the URL
as

http://www.shiv.com/(anf63t87iq0arjlqla2l55)/cutomdetails.aspx

 

[ashish]

The Expires property of the HttpCookie class makes a cookie persistent and
sets a date when a cookie will expire.
A persistent cookie enables a website to remember you on subsequent visits,
speeding up or enhancing your experience of services or functions offered.

you can also set things in web.config.
a Cookie is automatically in memory anyway.

Store what every info you want in a cookie and it is good to encrypt your
cookie also
Thanks
Ashish Shrivastava Chanderi

 

[elizas]

Cookieless Session in ASP.NET

The Session state in any web technology depend on cookie at the client end to store and resend session id back and forth between client browser and web server.
But Asp.net also supports cookieless sessions with the following attribute addition in the web.config within system.web node.


With the above config setting, it carry the session id in the page url instead of cookie.