By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,717 Members | 1,276 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,717 IT Pros & Developers. It's quick & easy.

How does Output Cache affect an SSL (https://) connection?

P: n/a
How does the ASP.NET output cache affect an httpS:// (SSL) connection?

Suppose I have a default.aspx page that has the following:

<%@OutputCache Duration="3600" VaryByParam="None" %>
Page_Load {
/* if 443 convert to http:// via Response.Redirect(..........) */
blah ......redirect to a simple port 80 connection as opposed to a 443
blah
Response.Redirect("http://" + ......... )
}
I would be using the output cache because it's the main page of the website
and heavily hit.

And furthermore a user can access it via

https://www.domain.com/default.aspx

So, the question is, "This page is obviously cached because the Page_Load is
not doing the redirect.
But is the webpage information encrypted when it's sent across the wire from
the server to the client? And how will the two technologies SSL and Output
Cache affect the final web server performance?"

Thanks.



Nov 20 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.