Download & Extend
Secure Pages » Issues

Using Secure Pages with SSL over non standard ports (not 443)

Posted by gauravkumar87 on November 30, 2010 at 8:35pm
Project:Secure Pages
Version:7.x-1.x-dev
Component:Code
Category:support request
Priority:major
Assigned:Unassigned
Status:needs work

Issue Summary

Hello,

I have SSL working on my webserver on port 8100, hence my secure URLs are of the form https://mywebsite.com:8100.

I've configured SSL to work for the website over this port, is there a way that Secure Pages can work with this non-standard port?

FYI: The module works fine, when i use the port 443, but when i switch to 8100, the radio buttons on the Secure Pages admin page are greyed out which is understandable cause to test it redirects to https://mywebsite.com which is not valid in my case.

Any help will be appreciated. Thanks.

Login or register to post comments

Comments

#1

Posted by rupesh.j on May 23, 2011 at 6:24am
Version:6.x-1.8» 7.x-1.x-dev
Priority:normal» major
Status:active» needs work

Hi,

I am also facing the same problem as @gauravkumar87 facing.

Any help would be appreciated.

#2

Posted by SteffenR on January 23, 2012 at 8:50am

Do we have any effort on this case ?
We try to run securepages on our staging server with following setup:
HTTP-Pages served by: stage.domain.com
HTTPS-Pages served by: stage.domain.com:442 (443 is taken by www.domain.com)

While switching from HTTP to HTTPS on redirection we get a bad gateway error - sharing cookies / sessions works fine.
Example:
Login-Form ( destination in a non-SSL Page)
https://stage.domain.com:442/user?destination=node/61634

Error:

400 Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
Hint: https://www.stage.domain.com

SteffenR