In my network configuration, SSL is negotiated by the load balancer which then communicates with the servers in the cluster via regular old, port 80 HTTP. Within my app, then, I can't use any of the traditional means of detecting whether a request is under SSL protection (at least none that I know of).
I could handle it in my Apache virtual host, but not in an .htaccess file (b/c of how Apache works) and I want to give developers the ability to control and manage which pages need SSL and which do not. They do not have that kind of server-level access so the virtual host solution won't do for our needs. The "easy" solution I see is to update each link in each view that accesses a secure page so that it uses a fully qualified URI with the https protocol applied. That will also require that fully qualified URIs are applied to all links _on_ secure pages that target pages that do not need to be secure. It will work, but it's an awfully distributed solution. Is there any way to do this with routes? I haven't turned anything up in the docs or in searches that doesn't rely on environment detection and redirection. If it can't be done with routes, has anyone else solved this particular problem? I'd love to find a more contained solution, if at all possible. Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
