Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

400
Views
403 ERROR The request could not be satisfied

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

over 4 years ago · Santiago Trujillo
3 answers
Answer question

0

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/

over 4 years ago · Santiago Trujillo Report

0

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.

over 4 years ago · Santiago Trujillo Report

0

I had the same issue. It was WAF / Firewall which rejected the request. Try to disable that to verify.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!