Enable HTTPS in development environment by building a version of RequireHttpsAttribute which supports port numbers. about templates HOT 6 CLOSED

My original plan was to implement this for MVC 6 so it could be used in the development environment where you are most likely using a port number like localhost:5000 to get to your site. Currently I just disable HTTPS in Development. In Staging or Production, the standard RequireHttpsAttribute could be used which does not support port numbers.

I hadn't really planned to implement this for MVC 5 as in your link but it would certainly help. That implementation using X-Forwarded-Proto is certainly interesting and not something I was aware of. I've mostly used Azure. Is this a standard setup in an AWS load balanced environment? I'm trying to get a feel for how often people come across this HTTP header and need to make use of it.

from templates.

@RehanSaeed It's a thing in Nginx which includes AppHarbor and prob Mono deployments depending on the server. The F5 load balancer may also do this as I've seen it before on other on-premises hosting environments where load balancers strip SSL.

from templates.

Most people will be using IIS and will not come across this then. I would not be averse to adding a filter to the Boilerplate NuGet package however so people can use it if they need to.

Quick question, since you are using Nginx with Boilerplate. I would like to add an option in the MVC 6 template for web server, so imagine a check box for IIS and for Nginx. Enabling the IIS check box gives you a pre-configured web.config file. Having no experience with Nginx, what would that check box do?

from templates.

Sorry but I'm not using this framework. I just stumbled upon your todo list somehow and thought I could, share some code that might be useful.

from templates.

Really appreciate it @cottsak. I've updated the TODO list with 'Add an option to choose the web-server you are using IIS, Nginx etc.'.

from templates.

Linking related AppHarbor support item.

from templates.