> call d.SetOptionHTTPHeader
> array("X-Amz-Security-Token:",Str(AuthInfo.SessionToken))
No, no, no.
You can't simply add another header there.
All headers must be part of the signature process.
SetupAWS(AWSAccessKeyId as String, AWSSecretAccessKey as String, Region as
String, Service as String, Path as String, Domain as String, Verb as String,
HashedPayload as String = "", Headers() as String = nil, queryParameters() as
string = nil) as boolean
There is a Headers() array and your header must go there.
Name: value
Please include space after double colon and.
Than it can be included in plugin signature..
> Still not working. I’ve done this before but only with SDK’s such as mobile
> SDK’s or Java with JavaFX clients. I’m opening a ticket with AWS support to
> query on if the Session Token is required to be used in the signature or not
> as I’m not finding examples of using temp credentials specifically with the
> S3 REST API but I might be just missing it.
They may have a way to output the headers used, so you can compare to yours.
Also check the response from AWS as they often include what you sent and what
they calculated.
Sincerely
Christian
--
Read our blog about news on our plugins:
http://www.mbsplugins.de/
_______________________________________________
Mbsplugins_monkeybreadsoftware.info mailing list
[email protected]
https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
