First Numbers from CloudFlare
-
@JaredBusch said in First Numbers from CloudFlare:
Using a page rule like this will not impact the rack space can issue.
I didn't think so. But how is @aaronstuder seeing two images and I am only seeing one. I'm trying to figure out what could be different.
Are you seeing one or two?
-
One
-
@JaredBusch Chrome?
-
@aaronstuder
-
Something has to be different with Aaron's setup. But what could be unique? This is an odd one for sure!
-
@scottalanmiller Testing on my iPhone
-
I only see one image, FF on Win 10.
-
@scottalanmiller said in First Numbers from CloudFlare:
Something has to be different with Aaron's setup. But what could be unique? This is an odd one for sure!
Either way, enabling the Cloudflare rule will not fix our hurt this issue. Completely separate issues
-
@JaredBusch said in First Numbers from CloudFlare:
@scottalanmiller said in First Numbers from CloudFlare:
Something has to be different with Aaron's setup. But what could be unique? This is an odd one for sure!
Either way, enabling the Cloudflare rule will not fix our hurt this issue. Completely separate issues
I had assumed, but when Aaron was able to see something that I could not I was hopeful that there was a fix out there related somehow that I wasn't understanding. But yeah, looks like there is sadly no relationship. So we can fix the "force to HTTPS" now. But RackCDN is going to remain another challenge.
-
@scottalanmiller said in First Numbers from CloudFlare:
@JaredBusch said in First Numbers from CloudFlare:
@scottalanmiller said in First Numbers from CloudFlare:
Something has to be different with Aaron's setup. But what could be unique? This is an odd one for sure!
Either way, enabling the Cloudflare rule will not fix our hurt this issue. Completely separate issues
I had assumed, but when Aaron was able to see something that I could not I was hopeful that there was a fix out there related somehow that I wasn't understanding. But yeah, looks like there is sadly no relationship. So we can fix the "force to HTTPS" now. But RackCDN is going to remain another challenge.
Mixed content is rarely an ussue
-
@scottalanmiller can you upload a valid certificate to the CDN? How many links are we talking about? Seems like it should be a small amount?
-
@aaronstuder said in First Numbers from CloudFlare:
@scottalanmiller can you upload a valid certificate to the CDN? How many links are we talking about? Seems like it should be a small amount?
That is not how it works
-
@JaredBusch I assumed this was the issue, no?
-
@scottalanmiller Would this fix it?
https://support.rackspace.com/how-to/using-cnames-with-cloud-files-containers/
-
@JaredBusch said in First Numbers from CloudFlare:
@scottalanmiller said in First Numbers from CloudFlare:
@JaredBusch said in First Numbers from CloudFlare:
@scottalanmiller said in First Numbers from CloudFlare:
Something has to be different with Aaron's setup. But what could be unique? This is an odd one for sure!
Either way, enabling the Cloudflare rule will not fix our hurt this issue. Completely separate issues
I had assumed, but when Aaron was able to see something that I could not I was hopeful that there was a fix out there related somehow that I wasn't understanding. But yeah, looks like there is sadly no relationship. So we can fix the "force to HTTPS" now. But RackCDN is going to remain another challenge.
Mixed content is rarely an ussue
I was more just grasping at straws combined with wishful thinking.
-
@aaronstuder yes , but your solution is wrong
-
@aaronstuder said in First Numbers from CloudFlare:
@scottalanmiller Would this fix it?
https://support.rackspace.com/how-to/using-cnames-with-cloud-files-containers/
Sadly it says:
"At this time, CNAMEs do not work with SSL (or HTTPS) delivery."
-
@scottalanmiller Damn it. How many images are affected?
-
@aaronstuder said in First Numbers from CloudFlare:
@scottalanmiller Damn it. How many images are affected?
By the RackCDN issue? Under 200, I'm pretty sure. And about ten are huge (meaning they get hit all of the time.) The rest are infrequent (just images used once on a page buried somewhere.)
So fixing all.... a pain. Fixing the low hanging fruit? Might be doable. At least we could get 99% of pages to not get an error from mixed content.
-
I'm going to start testing moving off of RackCDN for the big stuff tonight. See if that helps.
