PCF moving to SSL (2 Viewers)

Status
Not open for further replies.

Tommy

Royal Flush
Admin
Moderator
Supporter
Joined
Mar 23, 2013
Messages
18,513
Reaction score
46,010
Rewards
293
Location
Delaware
CCA#
R-8577
2016-12-28_15-04-14.jpg


While just the login/registration pages for a forum should have it, I'm prepping the site for a full-time SSL connection. I'm working on updating the last bit code so it doesn't give the user any mixed security warnings from static images, scripts, etc.

Sites not moving to an SSL connection will be taking a hit in the search engine rankings or as Google puts it, sites using SSL will have more favorable results.

Starting Jan 1st, anyone accessing a http://www.pokerchipforum.com/ URL will have it automatically re-write to the SSL connection URL.

2016-12-28_16-18-44.jpg


You can update your bookmarks now or just make a new one after the change.
If you experience any problems, please let me know.

Thanks!
 
Hmm I will have to look into this for my companies online store/website. It's SSL secured but I think its only the checkout pages not every single product page because you don't enter anything in on those pages. Wonder if this will still apply...
 
Hmm I will have to look into this for my companies online store/website. It's SSL secured but I think its only the checkout pages not every single product page because you don't enter anything in on those pages. Wonder if this will still apply...

Many sites are moving to full time SSL, but only the pages that collect payment info and passwords require it so you should be fine.
 
Many sites are moving to full time SSL, but only the pages that collect payment info and passwords require it so you should be fine.
The days of TLS being computationally expensive to implement on both ends of the connection are past as is the need to buy extremely expensive certificates. There are now many certificate options at various price points depending the exact features required. Didn't used tone that way.

Other than making shared web hosts using the same ip for multiple sites impossible a full time HTTPS site is actually simpler to implement.
 
I hope SSL is in no way related to SOL.
 
Just FYI... After we move to SSL there is only going to be 3 ways to add pics to your posts.

insert-images.png

  1. Upload/Attach them directly to your posts (Highly Recommended)
  2. Insert/Link them from your PCF Gallery (Good Option - The images will break if you delete the photo from your gallery though)
  3. Insert them from an external URL (Not Recommended - If the 3rd party host has issues, a policy change, etc., the image urls could break)
Note: Images posted using Option 3 will be cached and served via the PCF image proxy server using SSL.

Basically the same 3 ways that I've been preaching so not really a big change but some have been doing it another way so please keep reading.

Using the image url (right click - copy image address) from photos that were already posted using option 1 will only show to members logged in because they are being called from a protected core directory.


Example:
Code:
[IMG]http://www.pokerchipforum.com/attachments/photo-name-here.jpg.00000/[/IMG]

Images posted that way prior to SSL move, will show as blocked images.
2016-12-29_18-46-03.jpg


This is because the image links are hard coded into the post with http:// and not https://
They can be fixed by adding the 's' but keep in mind those images are still being called from a protected core directory and will only show to members who are logged in.

It is much better to just use option 1, 2 or 3.

If you come across any blocked images after Jan 1, just report the post and I will take care of it.

Thanks!
 
Thanks Tommy. Though I don't understand much about this type of stuff, it is clear you are passionate about continually enhancing the PCF platform. Considering how much your site means to many of us, your effort is truly appreciated.
 
One more thing, especially with Chrome users, you may have to clear your PCF cookies and do a hard refresh (ctrl + F5) if you have any login issues.
 
Note: Images posted using Option 3 will be cached and served via the PCF image proxy server using SSL.
If I understand this correctly then there's no point anymore in hosting my HQ-Pics externally to avoid load on your server because the PCF-proxy is taking care of them anyway? And updating pics on my server has no effect as the proxy shows the cached image and not the live one?
 
If I understand this correctly then there's no point anymore in hosting my HQ-Pics externally to avoid load on your server because the PCF-proxy is taking care of them anyway? And updating pics on my server has no effect as the proxy shows the cached image and not the live one?

It will not permanently store the images on the server as an attachment to the post. It stores them on the server for a cached amount of time (that I can set) before re-fetching & re-downloading the image.
 
Thanks Tommy - fast as lightning.
So it still saves the permanent storage space but bandwith not so much. How's the threshold for refreshing the proxy roughly set?
 
Thanks Tommy - fast as lightning.
So it still saves the permanent storage space but bandwith not so much. How's the threshold for refreshing the proxy roughly set?

I'm still looking over the settings for it. You can still post links to your images instead of loading them in the post with the IMG tag.
 
You can still post links to your images instead of loading them in the post with the IMG tag.

(y) :thumbsup: Yup, I used this workaround already in a conversation where the updated pic won't show (and still doesn't after 14 hours).
 
Status
Not open for further replies.
Back
Top Bottom