The new version of the router is written in Go and no longer uses nginx. It assumes that SSL termination is done at a load balancer in front of Cloud Foundry routers. Examples of something capable of doing this include F5, Zeus, AWS ELB's, etc. The Cloud Foundry router looks for and passes along X-Forwarded-For and X-Forwarded-Proto so that the apps that run in the DEA's get those headers.
CF.com still using v1 components has been running the GoRouter in production since near the beginning of the year.
The GoRouter has demonstrated much higher scalability in our tests than the previous version that was a combination of nginx, lua and ruby.
You may still be able to use the previous nginx based router and get it to do SSL termination, but it is no longer being maintained or tested and we did not do CF.com SSL termination with it.