Closed (fixed)
Project:
Secure Pages
Version:
5.x-1.6
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Apr 2008 at 01:33 UTC
Updated:
3 Aug 2008 at 04:22 UTC
This is my first patch submission to Drupal (or anything for that matter), so please be gentile.
Numerous webhosts only offer a shared SSL solution, and paying for certificates (or separate IP addresses) is not an option for everyone. This patch to Secure Pages allows the use of alternative ports, hosts, or base_urls for secured pages only, to make it easier to work around these issues.
Attached is the diff of the securepages.module file.
| Comment | File | Size | Author |
|---|---|---|---|
| securepages.module.diff | 3.58 KB | teaguesterling |
Comments
Comment #1
kkretsch commentedHow is the status of this patch? Anyone using it? Thats the feature I really would need for my sort of hosting provider.
Comment #2
zareen commentedYes. I could use this too. Would someone please turn this into a module that allows shared ssl, not just from a subdirectory, but from other site on server. Like, my ssl points to https://mysecuresite/!user
Thanks in advance!!!
Comment #3
scottrigbyHi, I just posted a question about whether it's possible to use this module using a shared secure server (here).
I have a very similar URL.. the shared secure server is formatted this https://mysecuresite/~username
Has anyone found a solution to this? or perhaps this patch will work with some slight modification?
It'd be really fantastic for any advice on this–
:) Scott
Comment #4
gordon commentedI have implemented my own method of doing this.
ATM it does not pass session so it will not work for shared SSL hosting.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.