Marli wrote:
> Yes, on top of that, I have _another_ problem with
> sfSslRequirementPlugin too (maybe someone should compile a list :-).
>
> Not many projects actually have an SSL certificate for their own
> domain (especially if you are on a shared host for example or if you
> are using port-based SSL virtual hosting). sfSslRequirementPlugin only
> switches the protocol to https - it would be nice to be able to
> specify an SSL and non-SSL url in config so the plugin could be used
> to switch SSL on and off for web sites that have a different SSL
> domain than their regular domain.
>
> I added this functionality myself to the version of the plugin I use
> but again it is quite hackish (and adding extra functionality yourself
> means you're always wasting effort redoing it when new versions are
> released, etc). This feature would be very handy in real-world hosting
> situations.
what i added to the current released version was a check against
sfConfig::get('app_disable_sslfilter')
you can set this config option on a per environment basis, this is what
i use to differentiate dev from prod.
regards,
Lukas
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" 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/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
