Hello
I'm having a problem with a web service and a client that communicates over HTTPS. The problem is that the Application_BeginRequest of the web service does not seem to be fired when I access it more than once.
This would imply some sort of caching going on (see here) but this blog states that when the communication is on a secure channel, such as HTTPS, no caching will take place.
I was thinking that maybe it's the client (a winapp) that does the caching. Does anybody know if this is possible, and if so, how do you stop it. This doesn't really sound plausible to me though, after all what would be the point of client side caching of a web service?
Anyways, I would appreciate any enlightenment on this subject.
I'm having a problem with a web service and a client that communicates over HTTPS. The problem is that the Application_BeginRequest of the web service does not seem to be fired when I access it more than once.
This would imply some sort of caching going on (see here) but this blog states that when the communication is on a secure channel, such as HTTPS, no caching will take place.
I was thinking that maybe it's the client (a winapp) that does the caching. Does anybody know if this is possible, and if so, how do you stop it. This doesn't really sound plausible to me though, after all what would be the point of client side caching of a web service?
Anyways, I would appreciate any enlightenment on this subject.