Support for S3 session keys#108
Conversation
According to the RFC 2616, a 301 Status Code only "SHOULD" return the new URI -- not "MUST". http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2
|
A new Pull Request was created by @holzman for branch cms/3836513. @cmsbuild, @smuzaffar, @Degano, @iahmad-khan, @davidlange6 can you please review it and eventually sign? Thanks. external issue cms-sw/cmsdist#2008 |
|
@smuzaffar @davidlange6 Chris and I would really like to see this go into a 7_6 release so that we can start testing with it. Can we start the process by putting it in 8_0_X ? Sorry we can't make the ORP today. Thanks, Liz |
|
I believe the integration tests are ongoing
|
|
@sextonkennedy @davidlange6 Yes, you can check the progress here: cms-sw/cmsdist#2009 (that's only a dummy PR to check the content of this patch.) |
|
jenkins tests looks good |
This branch fixes a bug in TWebFile (infinite loop when getting an HTTP Error 301), but more importantly adds support for AWS S3 session tokens (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html).
These were submitted to vanilla ROOT also under these PRs:
root-project#108 and root-project#110