@amrmostafa800 Isnt this in the source, and the token is after 'length','?
Just parse it.
@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.
@najort brazil?
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:
"Birthday=<YEAR>"
you'd change to
"Birthday=<DATA>"
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.
"fcmToken":"e98OtfFW1ZU:APA91bHeSDE0ZGF3CKJv8QpOxCCI0Dw_sRZA9fEcACVRjs-_EcsZchynCYjtF2q6OUV_9miCF2tlzJzi1xHtQqKEkqhw2neHet55gK9P2LSqYIRKtrMlBSzmqNavokV6rIOjpDSAPhJb"
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?
@test_it Please send this text from your print to us.
@Hakka If using
PARSE "<HEADERS(Authorization)>" LR "" "" -> VAR "AUTH"
I'd just try:
PARSE "<HEADERS(*)>" LR "\"Authorization\": \"" "\"," -> VAR "AUTH"
Or if that does not work, try:
PARSE "<HEADERS(*)>" LR "\"Bearer " "\"," -> VAR "AUTH" "Bearer " ""
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.
@test_it please copy paste the text for us to have as an example.
And your final output needs to be each name on a different line in a file?
Anyone ever dealt with this issue while making a config?
Received invalid cookies 'Secure; HttpOnly' from the HTTP-server 'www.site.com'