Inconsistent cookie issue - IIS4

[changed]

I'm having an inconsistent problem involving cookies. I have attempted to
duplicate the OS/browser settings for the remote users in question but I
cannot seem to duplicate the problem in any OS (Mac, Linux, Windows). I've
gone over and visited one problem site and I couldn't get it to work by
playing with security and privacy settings in MSIE. Obviously there is a
setting somewhere but I can't find it.

I can duplicate the problem by commenting out the ASP code that sets a
particular cookie. I also didn't see the cookie get set on the problem
system when I was trouble-shooting. I can't have the problem system with me
when I code though. :(

I won't post the entire project, but here are the parts that seem to be
central to the problem...

<%
Response.Expires=-1
Response.AddHeader "Pragma", "no-cache"

response.cookies("epeid") = value '40 characters
response.cookies("epeid").Expires = dateadd("n", 7, date() & " " &
Time())
response.redirect redirectURL
%>

It works fine on my systems. It redirects on the problem systems, only they
act like the cookie doesn't exist. When I asked the computer to prompt me
for each cookie I never saw epeid. On my system when I ask for a prompt it
just stalls on that particular cookie.

The above code is executed before any headers are written.

Thanks for any advice!

--
Mike

[changed]

"changed" <ch*****@changed.com> wrote in message
news:bj**********@geraldo.cc.utexas.edu...

It works fine on my systems. It redirects on the problem systems, only they act like the cookie doesn't exist. When I asked the computer to prompt me
for each cookie I never saw epeid. On my system when I ask for a prompt it just stalls on that particular cookie.

I found the problem. In this particular step I was writing a cookie with
ASP and then writing another cookie with JavaScript in the same page
request. Both cookies would be used immediately after the redirect. The
redirect would not work consistently with any machine although the chances
of success improved with newer/better machines. The ASP cookie didn't need
to be written in this step (I was doing it at every step, now it's done at
the first step) so I stopped writing it and everything works fine.

I think ASP cookies and JavaScript cookies don't get along if they are being
written in the same instance of a page request.

--
Mike