forked from TrueCloudLab/frostfs-s3-gw
#2 Fix AWS V4 signature regexp
We now respect possible spaces in parts of Authorization header field whoses presence causes problems for some client apps (such as aws cli). Signed-off-by: Pavel Korotkov <pkorotkov@gmail.com>
This commit is contained in:
parent
feaa52ae81
commit
d2ce83a6f8
1 changed files with 1 additions and 1 deletions
|
@ -18,7 +18,7 @@ import (
|
|||
"go.uber.org/zap"
|
||||
)
|
||||
|
||||
var authorizationFieldRegexp = regexp.MustCompile(`AWS4-HMAC-SHA256 Credential=(?P<access_key_id>[^/]+)/(?P<date>[^/]+)/(?P<region>[^/]*)/(?P<service>[^/]+)/aws4_request, SignedHeaders=(?P<signed_header_fields>.*), Signature=(?P<v4_signature>.*)`)
|
||||
var authorizationFieldRegexp = regexp.MustCompile(`AWS4-HMAC-SHA256 Credential=(?P<access_key_id>[^/]+)/(?P<date>[^/]+)/(?P<region>[^/]*)/(?P<service>[^/]+)/aws4_request,\s*SignedHeaders=(?P<signed_header_fields>.+),\s*Signature=(?P<v4_signature>.+)`)
|
||||
|
||||
const emptyStringSHA256 = `e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855`
|
||||
|
||||
|
|
Loading…
Reference in a new issue