403 ERROR The request could not be satisfied

Question

I have a website with a single quote, which I am not able to browse, and few with the same character on same domain it's getting redirected and I am able opens the URL.

l'Union-Européenne-Dans-l'Europe/xxxxx.html when removed the single quotes from url I am able to browse.

Result when tried to browse: 403 ERROR The request could not be satisfied. Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. Generated by cloudfront (CloudFront) Request ID:

Note: checked on clodfront access logs I could find the log with error code 403, not much information other than URI results /l%27Union-Europ%25C3%25A9enne-Dans-l%27Europe/xxxxx.html

Solution 1

Check your CloudFront configuration. This will occur because of below reasons:

1. The request is initiated over HTTP, but the CloudFront distribution is configured to only allow HTTPS requests.
2. The requested alternate domain name (CNAME) isn't associated with the CloudFront distribution.

You can refer this link also to resolve your issue: https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cloudfront-bad-request-error/

Solution 2

Posting my solution here because this was an arduous, weekend-long issue for me, and the solution was not that obvious. As Mani Ezhumalai's answer mentioned, the issue was alternate CNAME records needed.

In my case, it was www.example.com vs example.com. CloudFront requires both domains to be covered in the alternative domain names list, which requires a single AWS ACM SSL cert to cover both, as well as the appropriate CNAME records configured in the DNS.

Comments

[Jeremy Caney]

This is a good summary of why this happens, and probably infers the solution. But can you edit your answer to also summarize the steps suggested by the AWS documentation? While links are welcome, answers should remain relevant even if the page the link points to is removed or renamed at a later date—as frequently happens! By summarizing the steps, you help ensure your answer remains useful for future readers, while simultaneously saving readers today the need to click through to yet another page.

[radihuq]

Reason #1 was the issue for me. Quick solution: add https:// in front of the CloudFront domain

[radihuq]

Back again... this time I forgot to update the CNAME. Thanks

[codeaprendiz]

@radihuq, can you please elaborate ? How are you adding https:// infront of cloudfront domain :) ?

[BananaNeil]

I had not added an "alternate domain" to the cloudfront distribution in the control pannel. While doing it, I also needed to "request a certificate", and then attach that to the cloudfront distribution. "general" => "edit"

[karlos]

me it was cname as indicated thanks.