Signature expired: 20210305T000000Z is now earlier than 20210305T090919Z (20210305T091419Z - 5 min
what might be the problem.
SET VAR "KEY" "iEJ7zQkJ3i0m77Udq89Wa5gxl8y1lcLIUwE9bGaS"
SET VAR "DATE" "20210305"
SET VAR "REGION" "eu-west-1"
SET VAR "SERVICE" "execute-api"
UTILITY Conversion UTF8 BASE64 "AWS4<KEY>" -> VAR "KSECRET_B64"
FUNCTION HMAC SHA256 "<KSECRET_B64>" HmacBase64=TRUE KeyBase64=TRUE "<DATE>" -> VAR "KDATE_B64"
FUNCTION HMAC SHA256 "<KDATE_B64>" HmacBase64=TRUE KeyBase64=TRUE "<REGION>" -> VAR "KREGION_B64"
FUNCTION HMAC SHA256 "<KREGION_B64>" HmacBase64=TRUE KeyBase64=TRUE "<SERVICE>" -> VAR "KSERVICE_B64"
FUNCTION HMAC SHA256 "<KSERVICE_B64>" HmacBase64=TRUE KeyBase64=TRUE "aws4_request" -> VAR "KSIGNING_B64"
UTILITY Conversion BASE64 HEX "<KSIGNING_B64>" -> VAR "KSIGNING_HEX"
FUNCTION ToLowercase "<KSIGNING_HEX>" -> VAR "SIGNATURE"
I want to add:
It only** does the requests that you tell it to do as good as possible (while obeying to the basic standard, like having a Hosts Header)
And store the answer in the Variable <SOURCE> and as a extra service, it also automatically parses some stuff like Cookies, Headers, the Statuscode and so on to Varlables
**= this does not include selenium
@Ruri said in How to tackle protobuf:
We're working on it, but it's hard because you have to know in advance how the data types look like and compile the schema using the protobuf compiler. It's not something you can do on the fly, it needs pre-planning.
Thanks for trying! you can make it an option that the user can define their own schema or .proto file!