For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

mblachford_3582's avatar
mblachford_3582
Icon for Nimbostratus rankNimbostratus
May 30, 2018

HTTP::respond and header request modifications

Hey everyone. Trying to federate AWS S3 and an on premises S3 compliant storage box with iRules/iRulesLX. The calling client connecting to the BigIP will by default have the access key and secret ...
cloud
devops
iRules
iRulesLX
Simon_Blakely's avatar
Simon_Blakely
Icon for Employee rankEmployee
May 31, 2018

So the 302 response from your irule has an incorrectly formatted Location header with no protocol or URI, as I mentioned earlier.

Your new location header should be

https://s3.amazonaws.com/testbucket1/shot.png

HTTP::respond 302 noserver Location "https://$host[HTTP::uri]" Authorization "$authorization" X-Amz-Date "$xamzdate" X-Amz-Content-Sha256 "$xamzcontentsha256"