Even Rouault

"CURL_INFO_TEXT: Closing connection -1" is really intriguing I've pushed commit 90583a30a6d7e361239fe7cf4119b9d75c95239f with extra debug messages. Can you try with that ``gdalinfo /vsis3/MYBUCKET/myfile.jpg --debug on --config CPL_CURL_VERBOSE YES`` and possibly ``gdalinfo...

ok so psResult->nStatus = 3 matches the following Curl effort: CURLE_URL_MALFORMAT, /* 3 */ So something is wrong in the encoding of the URL. Are there "special" (ie non alphanumeric)...

ah sorry, I actually messed up my cherry-picking from the debug branch to the regular one. So please try with commit a115adb56bfe4e569c92893859c48a21f8753607 But I'm not super confident this will work....

ok, so there's a bit of progress as now the AssumeRoleWithWebIdentity works. I suspect the issue up to now was the trailing EOL character in the token file (that is...

@ashangit Thanks for the hint. I've tried to incorporate your suggestion of using header based authentication rather than through query parameters in commit 398fe487d56c29d19a09765f9b3c48529c68812b Could you / @m2rt test this...

Is my understanding correct that the osStsRootUrl + "/?Action=AssumeRoleWithWebIdentity&RoleSessionName=gdal&Version=2011-06-15&RoleArn=" + roleArn + "&WebIdentityToken=" + webIdentityToken HTTP request should use the value of role_arn from the source_profile (so here role_arn =...

perhaps @ashangit can help clarify ?

@ashangit Isn't the request of that ticket just a variation of what you've implemented when AWS_ROLE_ARN and AWS_WEB_IDENTITY_TOKEN_FILE configuration options are set from [profile webidentityprovider] ? > One side note...

> So should be recalled, no? ah indeed

Many years ago, I disabled in 1d0d64b67ebe1fec2e185718c2da123c5c3dba90 the use of binary cursors that was available through the "PGB:dbname=...." connection string with this commit message "PG: [...] disable code that was...