Open Darbiol opened 2 years ago
I had the same issue, got
'accept' is named as a SignedHeader, but it does not exist in the HTTP request.
It turned out I used the wrong URL for the connection. In my case, the good URL looked like
https://jr6rvrdasnehzdkg7dtraihflq.appsync-api.us-east-1.amazonaws.com/graphql
Do you want to request a feature or report a bug? bug?
Which versions and which environment (browser, react-native, nodejs) / OS are affected by this issue? Did this work in previous versions? react
Issue: I'm setting up an unAuth request using
AWS_IAM
with AWSAppSyncClient and react-apollo but i'm getting this response.Packages used:
Setup:
where we call the setup:
Where its being used:
Note: I've already setup Appsync to accept unauth request, also setup the unauth Identity and added the
@aws_iam
directive to my appsync schema.this is the request being sent
from what i understand from the error it's sending adding
accept
as a signed header but accept is not included in the calculation of the signature? is there a way we can remove theaccept
from SignedHeaders in the authorization?