Environment versions
Network:
Windows 2000 Server
>>
>>Danijel,
>>
>>Does this portion of your web site use SSL? Are you certain that the problem lies with client-side caching?
>>
>>The reason I ask is that there are no browsers/proxies that I am aware of that will cache anything in an SSL stream.
>>
>>There is a server-side (IIS) caching directive that has attributes that can be set in each page called @OutputCache. See "cache, ASP.NET Caching Features" in the VS.NET help files.
>
>Keith,
>
>As I mentioned at the end of my original post, my app does not use SSL, while the external site for verification of credit cards does. That is also the reason I believe it is a caching problem, as the final step is performed back in my app where registration is to be completed and funds withdrawn, all this done without SSL.
>
>I will check out OutputCache alternative, thanks.
Oops! I should pay more attention :)
The @OutputCache docs are fuzzy in some respects. The @OutputCache attribute doesn't affect browser caching, only IIS/Aspnet caching. Perhaps there is a standard meta-tag that instructs client-side browsers/proxies to not cache the web page.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only