Here's a sample snippet of what my assets.yml looks like:
embed_assets: off
package_path: newassets9
compress_assets: on
gzip_assets: on
javascript_compressor: closure
s3_access_key_id: ACCESS_KEY_ID
s3_secret_access_key: SECRET_ACCESS_KEY
s3_bucket: jammit-s3
s3_cache_control: public, max-age=<%= 365 \* 24 \* 60 \* 60 %>
use_cloudfront: invalidate
cloudfront_dist_id: DISTID
cloudfront_domain: domain.cloudfront.net
cloudfront_cname:
- cname1.mydomain.com
- cname2.mydomain.com
- cname3.mydomain.com
- cname4.mydomain.com```
The issue that I'm running into is that when cloudfront_cname is set, for some reason it is attempting to request https://cname1.mydomain.com rather than http://cname.mydomain.com. This is in the development environment, which isn't running on SSL right now at all.
Any ideas what might be causing this/how to fix? Right now I can just put a ssl: false line in my config and that seems to fix it, but I'm concerned that isn't a permanent fix, as it will cause SSL pages to request non-secure resources when I deploy to production.
Here's a sample snippet of what my assets.yml looks like: