Invalid Redirect message

[Keith A]

Originally Posted by fkelly

granted that "https" rather than "http" is needed.

However my bookmark is set to https and I still get the message.

It looks like all the links on the page(s) are set to "forums.paceline.net ..." rather than the full "https://forums.paceline.net" For instance in composing this reply I have a little indicator "Logged in as fkelly" where "fkelly" is a link field and down in the bottom left of the browser the link shows as: "forums.paceline.net/member.php?u=31555" Likewise the link for Log Out shows as "forums.paceline.net/login.php?do=logout .. then a hash key. I wonder if there is some way of forcing the https in these links.

Thanks for the follow up. I thought I was correctly forcing https, but apparently this isn't working correctly after the server relocation. I will work on getting this fixed.

[fkelly]

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.

[Shoeman]

Mine is working just fine now

[Keith A]

Originally Posted by fkelly

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.

Thanks for the link. I've read a bunch of different articles on this, but haven't seen that one yet. We are using GoDaddy for the domain registration, but they aren't hosting the site.

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.

[Bud_E]

Originally Posted by gone

Really simple (user) fix:

1. Log out
2. Google "paceline forum"
3. You'll see a match "Paceline forum powered by vBulletin" that has a link below it that starts "https..."
4. Click on the link
5. Log in
6. Done

+1 . Worked for me!

[regularguy412]

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

[palincss]

Originally Posted by regularguy412

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

And it's still http rather than https -- and that works now without an error message because the admins fixed whatever the problem was!

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...

[Keith A]

Originally Posted by regularguy412

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

As palincss mentioned, this should really be "https" instead of "http".

[jamiec]

Originally Posted by Keith A

Thanks for the link. I've read a bunch of different articles on this, but haven't seen that one yet. We are using GoDaddy for the domain registration, but they aren't hosting the site.

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.

Keith, what are you using in htaccess to force https?

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]

[Keith A]

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.

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]

I didn't craft this myself, but this came from an experience web-programmer friend.

[Keith A]

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...

RewriteEngine on
RewriteBase /
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} ^www\.thepaceline\.net
RewriteRule (.*) http://forums\.thepaceline\.net/$1 [R=301,L]

One of the other things this is supposed to do is redirect "www" to "forums".

[jamiec]

Keith, the code below would take care of both. It would redirect all traffic to https://forums.thepaceline.net (including www)

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]

[Keith A]

Originally Posted by jamiec

Keith, the code below would take care of both. It would redirect all traffic to https://forums.thepaceline.net (including www)

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]

Thanks!!! I'll give this a try later on and we'll see what happens

[Keith A]

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"

[Keith A]

But it looks like the following does work correctly...

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]

So let me know if anyone still has a problem with this issue. All combinations I tried, correctly points this to the "https" site.