There are many, many things in configuration that can cause a browser to not
cache document/authentication as you're wishing. Frequently, when you try
to do something "custom" without knowing all the ramifications, it tends to
break things and make them less optimal.
I have no idea what your configuration is -- what's the application, how is
state represented and persisted, what authentication protocol is used,
whether the client is Intranet or Internet relative to the server, any
related network configuration between the client and server, what is the
browser's configuration for state persistence and auto-login, etc.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Tony Short" <tony.short.RemoveThis@nelsoncroom.co.uk> wrote in message
news:01ac01c3d92c$02b4fd30$a301280a@phx.gbl...
Thanks for your response. We have trtied to persist state,
by using a cookie. It works sometimes, but from other
locations the cookie gets lost sometimes. Any idea why
this might be, and how we can avoid that?
Thanks (in advance!), Tony
>-----Original Message-----
>You probably have authentication enabled for these
documents. Thus, it is
>expected to see 401.x as clients access resources. You
really can't stop
>the GET requests from the client as a part of
authentication other than
>turning authentication off, which probably isn't an
option for you.
>
>For example, suppose you have enabled Integrated Windows
authentication for
>the URL. This form of authentication is on a per-
connection basis, and
>almost always starts with at least one 401 response prior
retrieving the
>resource. If your server actively closes connections,
the 401 response will
>repeatedly happen as the browser re-authenticates.
Remember, HTTP is
>stateless, so the fact that a client authenticated on the
prior request
>means nothing for any following request... unless some
form of state is
>persisted, either in the form of a cookie, a TCP
Connection, etc.
>
>If you are concerned about bandwidth wasted by the 401
responses, you can
>configure those custom error response files to be smaller.
>
>--
>//David
>IIS
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>//
>"Anthony Short" <webmaster.RemoveThis@nelsoncroom.co.uk> wrote in
message
>news:01fa01c3d625$feb75e70$a501280a@phx.gbl...
>I've got a number of prblems with "protected" documents.
>I've traced these back through thwe weblog, and find that
>while the document is returned by IIS with a status 200
>response, the Internet Exlorer client then makes several
>further requests for the same document. These further
>requests are rejected (stats 401, or similar) - presumably
>because they don't include information necessary to
>authenticate the user (and cookies information sees to be
>dropped).
>How can I stop the 2nd (or 3rd/4th/5th) GET requests?
>(Only a single request is sent for images files, and only
>a single GET request is sent if the file is saved rather
>than opended by IE).
>Very grateful for any pointers!
>
>
>
>.
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Problems with multiple gets with Office documents