I have a site which has to be secure – is there a downside to having the [RequireHttps] attribute on the home controller?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a site which has to be secure – is there a downside to having the [RequireHttps] attribute on the home controller?
To answer your Specific question, there are only three downsides I can think of if you require Https on your HomeController.
There is an insignificant increase in server CPU per request.
(If this application is served to millions/billions of users this may not be insignificant over a specific time)
There is an insignificant increase in network activity per request.
(this also applies to number of requests over a specific time)
If your certificate ever expires, users will get a negative experience of your Home pages.