Yaroslav Shepilov

Hi, I'm planning to, but not in the nearest future, to be honest :( yosefy schrieb am Mo., 18. Mai 2020, 08:22: > hi @bugy :) > do you plan...

There is an API for starting a script and getting an execution status. So you could do busy waiting for the status after starting a script Yaroslav Shepilov schrieb am...

`/executions/status/{id}` will give you `running` or `finished` response `/history/execution_log/long/{id}` will give you full info about the script (the same as on history detail page)

Hi @yosefy I'll try to do in this or the next week

Oops, sorry Could you remind me please, why `/history/execution_log/long/{id}` doesn't work for you?

But there is also exitCode included. This is an example from script-server.net for me: ``` { "id": "20834", "startTime": "2021-01-27T13:19:32.733000+00:00", "user": "abcde", "script": "Ping", "status": "finished", "exitCode": -15, "command": "ping...

Hi everyone here. I'd like to share, that for the dev version I implemented XSRF protection (#79). This is **not** backward compatible from API perspective. Now clients should send `X-XSRFToken`...

Hi @matiasrivera, try using "username" cookie. It should be enough. But you would have to refresh it every N days

@matiasrivera I cannot see the attached image

Still not here. Please send it to my email: [email protected]