[fixed]https available again

[bad_brain]

alrighty, https is available again, it's a self-signed certificate so you have to add an exception in the browser..

[ayu]

yay ... finally ^^

[Stavros]

Anytime I try to connect to https suck-o I get redirected to plaintext suck-o. Is anyone else having this problem?

[bad_brain]

you are right, the problem was caused by the mod rewrite rules which forced the use of "www.", it directed to http://" onclick="window.open(this.href);return false;.

I have added new rules for https now and divided the rules (for http and https) dpending on the ports, so it works now. if someone is interested, here's low it looks:

Code: Select all

RewriteCond %{SERVER_PORT} =80
RewriteCond %{HTTP_HOST} !^www\.suck-o\.com [NC]
RewriteRule ^(.*)$ http://www.suck-o.com/$1 [R=301,L]

RewriteCond %{SERVER_PORT} =443
RewriteCond %{HTTP_HOST} !^www\.suck-o\.com [NC]
RewriteRule ^(.*)$ https://www.suck-o.com/$1 [R=301,L]

don't wonder if you have to accept the certificate twice, that's because the main site and the boards are actually independent sites...

[Lyecdevf]

Anytime I try to connect to https suck-o I get redirected to plaintext suck-o. Is anyone else having this problem?

Yeah, it asks you if you want to view the entire page or just the contents that can be encrypted. I am in some cyber caffe and just got this thing my self.

[bad_brain]

hm, the reason are most likely some images with hardcoded http:// URLs....will check this out when I have some spare time...

[Lyecdevf]

hm, the reason are most likely some images with hardcoded http:// URLs....will check this out when I have some spare time...

It is no biggy. You just have to click on "no" and that is it.