stcheng
11/7/2007 9:50:00 AM
Hi Chuck,
Any further progress on this? Please feel free to post here if there is
anything we can help.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Organization: Microsoft
>Date: Mon, 05 Nov 2007 02:50:49 GMT
>Subject: Re: Caching Binary Output
>
>Thanks for your reply Chuck,
>
>Based on my understanding, the http protocol's cache is specified through
>some header variables in request or response header collection. Sure, url
>(include querystring) will influence how the client browser cache the
>request. Normally, a cache will be generated for a fixed url, if anything
>in the url changed, it will retrieve response from server.
>
>Sincerely,
>
>Steven Cheng
>
>Microsoft MSDN Online Support Lead
>
>
>This posting is provided "AS IS" with no warranties, and confers no rights.
>--------------------
>>From: =?Utf-8?B?Q2h1Y2sgUA==?= <Chuck@newsgroup.nospam>
>>References: <9EB87EDD-E222-4135-A764-A4037A6A54DE@microsoft.com>
><B24F993B0C5F435EA114AF36874F472C@OfficeVista>
>>Subject: Re: Caching Binary Output
>>Date: Wed, 31 Oct 2007 07:06:05 -0700
>
>>Steven,
>>
>>I wasn't sure from section 14.9 how the browser identifies the request
for
>>caching or if the caching works the same for various content types. Does
>it
>>use the URL and any parameters but not form fields?
>>
>>If it uses the URL and parameters, I could change my code to not stream
>from
>>the original URL but redirect to somePage.aspx?UniqueContentID=1
>>
>>Which would probably get cached then (content type
>> aapplication/x-msdownload, application/pdf )?
>>
>>
>>
>>"Steven Cheng[MSFT]" wrote:
>>
>>> Thanks for Dave's input.
>>>
>>> Hi Chuck,
>>>
>>> The one you mentioned is client cache which is a feature of the http
1.1
>>> protocol. The ASP.NET Cache API(which set client cache ) actually use
>the
>>> "Cache-Control" http header to supply the http cache information so as
>to
>>> let the client browser know how to cache the response content. AS in
>the
>>> MSDN document said, you can look up the RFCC 2616- HTTP/1.1 spec and
>find
>>> the detailed description on "cache-control" in section 14.9
>>>
>>> Sincerely,
>>>
>>> Steven Cheng
>>>
>>> Microsoft MSDN Online Support Lead
>>>
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>rights.
>>>
>>>
>>>
>
>>> >
>>>
>>>
>>
>
>