UPS tracking broken again? about paketin-seuranta HOT 11 CLOSED

New thing added to this api is X-XSRF-TOKEN header, when I populated that it worked again. Otherwise giving un authorized. Now have to solve where to ask / calculate this token.

from paketin-seuranta.

from paketin-seuranta.

Where'd you get that one for testing?
…
On Sun, Nov 22, 2020, 11:54 Martin Kankaanranta @.***> wrote: New thing added to this api is X-XSRF-TOKEN header, when I populated that it worked again. Otherwise giving un authorized. Now have to solve where to ask / calculate this token. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#83 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJU4T5RZYRXAYESOZW566RDSRDNUPANCNFSM4T3DQPBA .

From @ristomatti at private Trello board so @ristomatti decides should it be shared for you

from paketin-seuranta.

Is the only right way to handle this via loading tracking page because it initially gives response header "Set-Cookie" having that token which is valid for X time. I'm not sure.

from paketin-seuranta.

@norkator Sure you can share it (privately). It's only my new laptop. 😄 But it'll be a home delivery anyway. To be delivered Monday/Tuesday I believe.

from paketin-seuranta.

Okay theres another way.. I stole this from Aftership website: 1ZA529F90495123295 @developerfromjokela

from paketin-seuranta.

Where'd you get that one for testing?
…
On Sun, Nov 22, 2020, 11:54 Martin Kankaanranta @.***> wrote: New thing added to this api is X-XSRF-TOKEN header, when I populated that it worked again. Otherwise giving un authorized. Now have to solve where to ask / calculate this token. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#83 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJU4T5RZYRXAYESOZW566RDSRDNUPANCNFSM4T3DQPBA .

From @ristomatti at private Trello board so @ristomatti decides should it be shared for you

I meant how did you find about the header? Or where?

from paketin-seuranta.

Where'd you get that one for testing?
…
On Sun, Nov 22, 2020, 11:54 Martin Kankaanranta @.***> wrote: New thing added to this api is X-XSRF-TOKEN header, when I populated that it worked again. Otherwise giving un authorized. Now have to solve where to ask / calculate this token. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#83 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJU4T5RZYRXAYESOZW566RDSRDNUPANCNFSM4T3DQPBA .

From @ristomatti at private Trello board so @ristomatti decides should it be shared for you

I meant how did you find about the header? Or where?

Just simply tested with chrome and noticed that token, then tried with rest client tool with Paketin Seuranta current config, got that permission denied and then with token which I copied from this browser request -> then it worked.

from paketin-seuranta.

This stupid X-XSRF-TOKEN-ST is what I am looking for, its calculated at Bundle javascript file when entering ups webpage. I try engineer how its done so can mimic it.

from paketin-seuranta.

I don't know why I think this so hard, if you call "https://www.ups.com/track?loc=en_US" with get method theres header in response with X-XSRF-TOKEN-ST

from paketin-seuranta.

Okay found out just by looking how ups page is actually handling these tokens so now theres header called Cookie with X-XSRF-TOKEN and its corresponding token and then own X-XSRF-TOKEN with X-XSRF-TOKEN-ST

from paketin-seuranta.