Project

General

Profile

Actions
Copy link

Bug #54181

closed

RGW does not support iso8601 date format in Date Header

Added by Dmitry Kvashnin about 2 years ago. Updated about 2 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
44915
Crash signature (v1):
Crash signature (v2):

Description

RGW checks only rfc2616 date format in header "Date".
When client uses iso8601 format, HTTP code=403

HTTP starting HEAD /fdb ContentLen:0
Request Header: Accept: application/xml
Request Header: Authorization: AWS foundation:e5MvaSCesn/juuy78mFSg5dubjc=
Request Header: Content-Length: 0
Request Header: Date: 20220207T143135Z
Request Header: Host: 192.168.119.11
[645a7ef8d7933054fa7fa638fcfa95b4] HTTP code=403 early=0, time=0.005275s HEAD /fdb contentLen=0 [172 out, respons                                                                                                                                                                 e content len 185]
[645a7ef8d7933054fa7fa638fcfa95b4] HTTP RESPONSE:  HEAD /fdb
Response Code: 403
Response ContentLen: 185
Reponse Header: Accept-Ranges: bytes
Reponse Header: Connection: Keep-Alive
Reponse Header: Content-Length: 185
Reponse Header: Content-Type: application/xml
Reponse Header: Date: Mon, 07 Feb 2022 14:31:35 GMT
Reponse Header: x-amz-request-id: tx00000205cd102d9c956b6-0062012d47-5e4d-default
-- RESPONSE CONTENT--
Actions
Copy link
 #1

Updated by Casey Bodley about 2 years ago

  • Status changed from New to Won't Fix

see discussion in PR

Actions
Copy link

Also available in: Atom PDF