Re: 1.2M6: Granular HTTPS Support

Would't this be best simply as a module? A module could keep a lookup table of
which URLs should  be secure, what the rules for switching between the two are,
hook into the page load event and do a redirect to the secure or non-secure
equivalent page if necessary. It could also set a global that affects the
protocol for all URLs generated on that page.

Adding a new parameter just seems wrong. It is putting the entire control into
the hands of the developer, with no way for the site administrator to decide
which areas of the site are to use secure URLs.

-- Jason