Can someone globally recommend disabling cookies and still have ASP work? Can anyone program aound the need for server-side cookie needed to update a web page? Does profiling and security pertain to ONLY clinet-side cookies?
HLotis:<br><br>>Can someone globally recommend disabling cookies and still >have ASP work? <br><br>Yes ASP pages will work. but if your page/application is using anything session/cookies that will not work. ASP is lot more that cookies. <br><br>>Can anyone program aound the need for server-side cookie >needed to update a web page?<br><br>Cookies facilities are given to store the information in client machine for a given tme so that you don't have come to server for everytning. page/application can work better way on being client itself. if application/page want server participation then why to write server side cookies complete server with all resources there to serve you. probably you misunserstood cookies.<br><br>Hope this is helpful to you.<br><br>Anand<br><br><br>
Dear HLotis,<br><br>> Can someone globally recommend disabling cookies and still have ASP work? <br><br>Wow, not sure what that means. Are you asking if ASP Sessions work when cookies are disabled? If so the answer is... Nope. From the MSDN online: <A HREF="
Sessions Are Cookie-based <br>ASP uses HTTP cookies to send users their unique session keys. <br><br>***********<br>> Does profiling and security pertain to ONLY clinet-side cookies? <br><br>Don't follow that question either. Could you could ask more specific questions? 'Profiling' and 'Security' are extremely ambiguous terms.<br><br>-pete<br>
PROFILING and Privacy - Microsoft announced today in the Washington Post page E8, that it Microsoft is coming out with an option that will allow a user or a site manager to block downloading a specific Clinet-side cookies or a domain of 3rd party cookie files. This is like an Outlook “rule” for junk mail; disallow receipt of specified e-mail names. I think, however, that all these “problem” cookies were at the client side! Server side cookies are required by IIS and are Mandatory. Server cookies are NEVER written to a user’s hard drive. They cannot be disabled and programmed around like you can with the client-side programmer generated cookies. They are just Server session variables in memory that disappear from memory at the end of a user session. Cookies cannot be summarily disabled if you are going to update a web page from a database. While most of DOI/MMS sites consist of static pages, there are several dynamic database applications that would stop immediately if cookies were disabled at an end-users PC. There is no way to program around Server side variables. Sever side cookies are not created by user written programs but are generated by functions within IIS and required by the IIS software! Client-side Profiling and privacy issues have nothing to do with Server-side cookies. Both sides use cookies. The programmable cookies are all client-side and generated by programmers. These are the ones being referred to by David Shearer.<br><br>Am I misunderstanding soemthing???
Can the organization globally recommend disabling cookies and still have my ASP pages work on our Intranet that require database values to update forms? The Orgn is worried about advertisers profiling users and the effect it will have on privacy and hacker security. I think the Orgn is confusing client-side cookies with server-side cookies. <br><br>See question at top of page.
HLotis:<br><br>>Can the organization globally recommend disabling cookies >and still have my ASP pages work on our Intranet that ><br>>require database values to update forms? <br><br>Yes, but decision of organisation will taking away some power of your application. Without cookies also we can make ASP application which work with Database and forms.<br><br><br>Anand
See above post from PAlbano which contains the final answer since it comes live from Microsoft online. <br> PAlbino restated "WillASP Sessions work when cookies are disabled?" He answered The answer is... Nope.<br><br>See the article form the MSDN online: <A HREF="
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.