noobaa / noobaa-core

High-performance S3 application gateway to any backend - file / s3-compatible / multi-clouds / caching / replication ...
https://www.noobaa.io
Apache License 2.0
268 stars 78 forks source link

Presigned URL inaccessible from browser after 15 minutes #7565

Open ndeahl opened 11 months ago

ndeahl commented 11 months ago

Environment info

Actual behavior

  1. Presigned URL for a GetObject request is generated via Golang using AWS SDK (also via AWS CLI) talking to noobaa instance.
  2. URL is generated, and the object is accessible and downloads from the browser for 15 minutes after URL generation time
  3. After 15 minutes, the object becomes inaccessible with the response code: RequestTimeTooSkewed.
  4. Object is still accessible via curl request when adding to the command: curl -H "X-Amz-Date: $(date -Is --utc)"

Expected behavior

  1. Presigned URL should still be accessible from browser after 15 minutes from generation time (as long as the expiration period is longer than that)
  2. Downloads still work without manually setting request header when accessing via an AWS S3 bucket

Steps to reproduce

  1. Create presigned URL for an object on a noobaa bucket: aws s3 --endpoint=https://noobaa-endpoint presign s3://prefix/to/object.csv --expires-in 172800
  2. Copy generated URL into browser and view that the object can be downloaded when navigating to that URL
  3. Wait 15 minutes and attempt to download file again, you should see the error response with code: RequestTimeTooSkewed

More information - Screenshots / Logs / Other output

image
github-actions[bot] commented 5 months ago

This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed.

github-actions[bot] commented 2 months ago

This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed.