79754397

Date: 2025-09-03 09:30:57
Score: 3.5
Natty:
Report link

This happened to me when I was working with S3 over a corporate proxy which stripped the "range" header, causing the sigv4 not to match because the headers changed. Do you possibly have something similar in place?

Reasons:
  • Low length (0.5):
  • No code block (0.5):
  • Ends in question mark (2):
  • Single line (0.5):
Posted by: Greg Olmstead