Asp.net Cookie Domain / Scope
<p>I have a "cookie" handler / utility class that works quite well for me. It abstracts away a lot of the issues that I drive me crazy when dealing with cookies such as how to handle a response (write) operation followed by a request (read) operation on the same postback, how to handle encryption, etc.</p>

<p>The one thing that eludes me is how to segregate my cookies across different “virtual” domains. My applications are running in an intranet environment all with the same host / server name:</p>

<p><a href="http://server/app1/" rel="nofollow">http://server/app1/</a></p>

<p><a href="http://server/app2/" rel="nofollow">http://server/app2/</a></p>

<p>I don’t want these different applications sharing cookie values in the event that they use the same names. Approaches on the Request / Response object?</p>
