79509686

Date: 2025-03-14 16:34:50
Score: 2
Natty:
Report link

In my case I was proxying a call with all the headers, which container "host" and it resulted in 403.
Removing all the unplanned headers solved the issue.
AWS is so unintuitive in those API GW errors.

Reasons:
  • Low length (0.5):
  • No code block (0.5):
  • Low reputation (1):
Posted by: Volodymyr