Bug #8130
invalidly formatted dates in listObjects fromDate / toDate parameters do not result in InvalidRequest
Start date:
2017-07-13
Due date:
% Done:
100%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
instead, the filters are not applied, and unfiltered results are returned.
The call should return an InvalidRequest error with explanation.
This is especially devious when someone doesn't escape the '+' in the timezone field, and it gets decoded to space, resulting in an invalid date format, and incorrect filtering.
Checking the svn logs on CNResourceHandler, (added in r6622) there isn't a specific reason it was put in, so it should be safe to change.
History
#1 Updated by Rob Nahf over 7 years ago
- Subject changed from poorly formatted dates in listObjects fromDate / toDate parameters do not result in InvalidRequest to invalidly formatted dates in listObjects fromDate / toDate parameters do not result in InvalidRequest
- Description updated (diff)
#2 Updated by Jing Tao about 7 years ago
- Target version changed from CCI-2.3.6 to CCI-2.3.7
#3 Updated by Jing Tao about 7 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Change the code to make it throw exception on both v1/v2.
#4 Updated by Dave Vieglais almost 7 years ago
- Sprint set to CCI-2.3.7
