> Now - once they are authenticated, and they request www.cisco.com again,
> they _still_ get the username/password page because it is cached.
> Obviously, if they request any other page, they get what they asked for.
>
> I'd appreciate any ideas as to how I can redirect to this
> username/password page while specifying that it is not to be cached.
There are two possibilities. You can write your username/password page
to be uncacheable. Or you can send a PURGE request to the cache once
authentication succeeds. The first is probably simpler/better, since
hopefully you won't get enough retries for caching to help the unauthenticated.
Jon
Received on Fri Jun 25 1999 - 04:32:56 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:46:59 MST