Yes, Anthony I was also thinking that the client cache might be
causing the problem, but again that seems to be unusual... Can you
please suggest a way to check this or a fix for this? I tried by
cleaning the browser cache. No luck.

Here's a bit more details of the problem: We have a page/code (say
Page1.aspx) that gets called for all client request and we apply
custom user authorization there. We are using a cookie to keep the
user credential information (combination of form authentication cookie
and some other custom information). This cookie is shared between
global.asax, Page1.aspx and client script. We create the cookie in
Page1.aspx, update it conditionally in global.asax and read it from
client script. When we try to read the value in client script, we are
seeing that it's having the value set in Page1.aspx. Even if we are
modifying the same cookie in global.asax, that value is not reflecting
in client script. As an alternative, if we create a new cookie from
global.asax, we can easily get the correct value. But we don't have
any clue of why it's behaving that way!