Closed hholzgra closed 2 years ago
Thinking again we can solve the "malicious user" problem by returning the already existing job nonce value as part of the job creation results, and only accept cancel requests that contain both the job id and correct nonce.
Thinking again we can solve the "malicious user" problem by returning the already existing job nonce value as part of the job creation results, and only accept cancel requests that contain both the job id and correct nonce.
Implemented now as POST endpoint "cancel_job" expecting parameters "id" and "nonce"
Just missing proper documentation now.
Documentation added, closing
Depends on Issue #6 to prevent malicious users from cancelling other jobs to get further up in the rendering queue