Hey guys,
Here's the puzzle for you:
So, asp.net will allow for cookieless session state, but that puts the sessionID in the url, and looks ugly. So I did a test:
I created an asp.net app with two pages. On one page, there's a button to create a session variable and assigns it a value. Then, I have buttons to move between the two pages, just to prove that the session variable is still alive.
I then make sure that my project web.config file is set to cookieless = "false", so the project wants to use cookies.
BUT
I set my browser to BLOCK ALL COOKIES. SO no cookies can be written or read to my machine.
Logic would tell me that the session variables shouldn't work...BUT THEY DO!!!
So my question is: if you have cookies blocked on your client, so the app can't write a cookie, and the sessionID doesn't show up in the url of the page, where does the sessionID get stored?!
Let me know what you come up with Sherlock
Jack
Here's the puzzle for you:
So, asp.net will allow for cookieless session state, but that puts the sessionID in the url, and looks ugly. So I did a test:
I created an asp.net app with two pages. On one page, there's a button to create a session variable and assigns it a value. Then, I have buttons to move between the two pages, just to prove that the session variable is still alive.
I then make sure that my project web.config file is set to cookieless = "false", so the project wants to use cookies.
BUT
I set my browser to BLOCK ALL COOKIES. SO no cookies can be written or read to my machine.
Logic would tell me that the session variables shouldn't work...BUT THEY DO!!!
So my question is: if you have cookies blocked on your client, so the app can't write a cookie, and the sessionID doesn't show up in the url of the page, where does the sessionID get stored?!
Let me know what you come up with Sherlock
Jack