The filter was called Cookie Munger. As I understand it, it did work but had
several drawbacks.
1. performance
The way it worked was to scan outgoing HTML content for links to ASP pages
and modify them to include the session cookie as part of the URL. On
incoming requests the URL was examined and the session cookie was added back
to the HTTP header. Incoming was not to bad but outgoing meant that every
page had to be parsed.
2. might not get every link
If you used JavaScript code to redirect the browser anywhere (as in
self.location=...) then you would not get a session cookie.
--
Mark Schupp
Head of Development
Integrity eLearning
www.ielearning.com
"Chris" <chris@hicom.net> wrote in message
news:kNnNb.39679$G04.9592002@news4.srv.hcvlny.cv.n et...[color=blue]
> I have a small ASP site running, which uses Session Cookies to support
> Session state.
>
> I'm being asked to get rid of the dependancy on the availability of
> session cookies.
>
> I know there'd been an ISAPI filter around that would put the session
> variable into the URL and links (what asp.net does to get cookieless
> sessions), but can't find any mention of it right now (when I need it!).
>
> 1) Has anyone heard of this kind of add-on, and
>
> 2) Should I just bite the bullet and pass my own session id around keep
> my own session data??
>
> -- Thanks[/color]