Here is the scenario, a user opens up non-secure page from our WebApp, let\'s call it PageA, in their browser and then clicks a link in there that takes them to a secure instanc
I've never tried it but you might be able to use the Outputcache VaryByHeader property and the "host" header, which specifies the Internet host and port number of the resource being requested.
The question I'd have is why are you redirecting to PageA over secure after from PageB. If its a non-secure page, couldn't you fix the PageB redirect to always redirect to non-secure.