Maximum skew request time inconsistent with S3

Bug #1498674 reported by Darryl Tam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Swift3
New
Undecided
Unassigned

Bug Description

Currently, the maximum allowed skew between the date of a request and the server time is five minutes. However, the maximum skew allowed by S3 is fifteen minutes (applies to all standard AWS regions).

Should we change the default skew to match? Should we make this configurable (with a maximum allowed value?

This is currently checked in the _validate_headers function in the Request class in request.py

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.