Authorization header not matching AWS examples

[billsanto]

On line 189 it shows a comma added between the first two fields.

httr2/R/req-auth-aws.R

Line 189 in e6f425e

Algorithm, ",",

In online examples on AWS documents, it shows a space separating the first two fields, whereas commas are used between the subsequent fields. Similarly, this online tool shows the same pattern.

[hadley]

Thanks! Is this causing auth to fail for you?

[billsanto]

I haven't tried directly against AWS. We have a proxy in front of Bedrock, and in the process of troubleshooting with them they pointed out the header was not conforming to the expected format. Maybe AWS is more forgiving in how it parses the header, but I don't know. That team updated the dev proxy for me to test, so we are past that as it now accepts the comma as is, but we are now at the stage of struggling to match signatures with a hacked provider-bedrock using the Invoke API, which is a separate issue.

I have successfully tested our proxy in R with httr and aws.signature when I construct the headers and signature. But when I'm using Ellmer, that is not an option.

[hadley]

I'm hoping to implement #435 soon, which might also help.

[hadley]

I'll fix momentarily. It's weird that AWS lets this work at all. Thanks for reporting!