#31
|
||||
|
||||
Quote:
|
#32
|
|||
|
|||
You've seen:
https://www.vbulletin.com/forum/arti...forum-to-https Hopefully we aren't using Godaddy I don't suppose it could be as "simple" as a htaccess rewrite of http to https? Though I've put entire sites out of operation (temporarily) by messing with htaccess. |
#33
|
|||
|
|||
Mine is working just fine now
|
#34
|
||||
|
||||
Quote:
I have been modifying htaccess, and I too have created some problems when messing with this file, and it always makes me a little nervous when I start changing these settings. I have with our hosting company, and they were somewhat helpful, but not as much as I'd hoped. |
#35
|
|||
|
|||
+1 . Worked for me!
|
#36
|
||||
|
||||
I just deleted my old shortcut and created a new one. Now it looks like this:
http://forums.thepaceline.net/forumd...daysprune=&f=3 Takes me right to the General Discussion first page. Mike in AR
__________________
2013 Serotta Fondo Ti w/Enve fork |
#37
|
|||
|
|||
Quote:
Speaking of which, I still wonder about that "dst" parameter in the redirect, sure seems like it might mean daylight savings time to me, and since we are no longer on daylight savings time that would be invalid... |
#38
|
||||
|
||||
Quote:
|
#39
|
|||
|
|||
Quote:
For all the sites I build I use the code below, It would go at top of you root htaccess file RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://forums.thepaceline.net/$1 [L,R=301] |
#40
|
||||
|
||||
Thanks for the help and input on this problem!!! I'm a software engineer who knows enough about web-programming to usually get myself in trouble.
Here's what my .htaccess file is supposed to contain, but I will need to check the current file contents to see if our hosting company has modified this file. Code:
RewriteCond %{HTTPS} off RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] RewriteCond %{HTTP_HOST} ^www\.thepaceline\.net [NC] RewriteRule ^(.*)$ https://forums.thepaceline.net/$1 [L,R=301] Last edited by Keith A; 11-15-2017 at 08:23 AM. |
#41
|
||||
|
||||
Looks like my current .htaccess file isn't what I set this previously. I know there are other ways to skin this https cat and will need to check with our host company and see what is going on.
Anyway, this is our current .htaccess file contents... Code:
RewriteEngine on RewriteBase / RewriteCond %{HTTP_HOST} . RewriteCond %{HTTP_HOST} ^www\.thepaceline\.net RewriteRule (.*) http://forums\.thepaceline\.net/$1 [R=301,L] |
#42
|
|||
|
|||
Keith, the code below would take care of both. It would redirect all traffic to https://forums.thepaceline.net (including www)
Code:
RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://forums.thepaceline.net/$1 [L,R=301] RewriteCond %{HTTP_HOST} !^forums.thepaceline.net [NC] RewriteRule ^(.*)$ https://forums.thepaceline.net/$1 [L,R=301] |
#43
|
||||
|
||||
Quote:
|
#44
|
||||
|
||||
When using jamiec suggested changes, typing in the following:
o "www.thepaceline.net" o "forums.thepaceline.net" o "http://forums.thepaceline.net" o "thepaceline.net goes to "https://forums.thepaceline.net/forums/" and not "https://forums.thepaceline.net" |
#45
|
||||
|
||||
But it looks like the following does work correctly...
Code:
RewriteCond %{HTTPS} off RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] RewriteCond %{HTTP_HOST} ^www\.thepaceline\.net [NC] RewriteRule ^(.*)$ https://forums.thepaceline.net/$1 [L,R=301] |
|
|