Set cookie domain to “example.com” Seems not Working
-
Hi Team,
While I was using W3TC on the local development machine, tried to serve the “Host attachments” from the Amazon S3 bucket. First time images refused to load. However, when I checked “Set cookie domain to “mylocal.subdoman.com” it worked fine (self-signed certificate is trusted for local development).
Now I am beginning to set up an actual site that has Letsencrypt issued certificate, I can’t load the image no matter what I do.
When selecting default option to use “<my_bucket_name>.s3.amazonaws.com”, my chrome says invalid certificate “NET::ERR_CERT_COMMON_NAME_INVALID”. When I checked, the certificate issued was “*.s3.amazonaws.com” (not my domain).
However, when I try to use the actual path like “s3.ap-south-1.amazonaws.com/<my_bucket_name>/” (on CNAME field), it works
So my question is why can’t I use the default subdomain option? It looks much cleaner. I named my bucket “cdn.mydomain.com”
Any suggestion?
Thanks!
- The topic ‘Set cookie domain to “example.com” Seems not Working’ is closed to new replies.