@amrmostafa800 Isnt this in the source, and the token is after 'length','?
Just parse it.
@Why001 That is the deal, there isnt any requests generating it. Unless this "encrypted" post-data that I showed at the end of the topic is what generates it. But I doubt to be honest.
And also, I'd just try
IF "<SOURCE>" Contains "Invalid Year" SET VAR "DATA" "<MONTH>" JUMP #REQUESTBIRTHDAY ENDIF IF "<SOURCE>" Contains "Invalid Month" SET VAR "DATA" "<DAY>" JUMP #REQUESTBIRTHDAY ENDIF
And obviously you'd need to set the DATA variable as the YEAR before the request, make the request, you can just use:
SET VAR "DATA" "<YEAR>"
And remember to use it as a parameter, like you said:
you'd change to
That's the answer based on the context you gave us.
Obs.: That's an incomplete example, there are a lot of other factors that you will need to consider before you make what I said.
Does anyone knows how this token is generated? I couldn't find any requests related.
The only requests I found that are made before this token, does not have any response and the post-data is weird, like it was "encrypted"
Well, anyone ever dealt with this?
I'm nor sure if you are aware, but you can use blocks inside IFS normally, without any problem. So, if you want, try this:
IF "<Singers>" MatchesRegex "[ABCD]" #request block #function block #parse block #keycheck block ... ENDIF IF "<Singers>" MatchesRegex "[ABCDEFG]" #request block #function block #parse block #keycheck block ... ENDIF
It's just an example so you can understand that you don't need to use only commands like SET with IFs. You can just use "nested" blocks, I don't know the right expression.
Literally just remove the
KEYCHAIN Success OR KEY "" status \ ": true"
from the Keycheck #1???????
Or if you want you can just write
SET STATUS NONE
after the block.