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.

CommentFileSizeAuthor
#5 securepages-non_standard_ports-985538-5.patch884 bytesmicnap
#4 securepages-non_standard_ports-985538-4.patch883 bytesmrmikedewolf
#3 securepages-non_standard_ports-985538-3.patch850 bytesjemond

Comments

rupesh.j’s picture

rupesh.j commented
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.

steffenr’s picture

steffenr
Primary language German
Location Bremen
commented

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

jemond’s picture

jemond commented
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new securepages-non_standard_ports-985538-3.patch850 bytes
mrmikedewolf’s picture

mrmikedewolf commented
StatusFileSize
new securepages-non_standard_ports-985538-4.patch883 bytes

Changing the url to an absolute link throws off drupal_goto unless the 'external' option is passed to url. I've modified the patch to account for this.

micnap’s picture

micnap commented
StatusFileSize
new securepages-non_standard_ports-985538-5.patch884 bytes

Patch wouldn't apply for me and we need to apply with drush make so recreated.

astonvictor’s picture

astonvictor commented
Status: Needs review » Closed (outdated)

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks