-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Batch jobs results: canonical link in canonical response? #508
Labels
Milestone
Comments
I think that's fine. I'd also assume that if you request the signed document later and it was updated in the meanwhile (e.g. status, title) it is also updated. |
Would you be up to create a PR for clairification? @soxofaan |
soxofaan
added a commit
to soxofaan/openeo-api
that referenced
this issue
Oct 9, 2023
Yes, I think #513 is not ideal. |
m-mohr
added a commit
that referenced
this issue
Dec 18, 2024
Co-authored-by: Matthias Mohr <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(related to #507 and Open-EO/openeo-aggregator#115)
Say
/jobs/{job_id}/results
has a canonical link, e.g./jobs/{job_id}/results?signature=123
.Can
/jobs/{job_id}/results?signature=123
contain another canonical link, say/jobs/{job_id}/results?signature=456
e.g. with updated expiry timestamp?Strict interpretation of
seems to forbid that: must be exact same document?
However, it would be useful for long term execution situations (and crossbackend execution) that the expiry of signed batch job result url can be bumped by this way.
The text was updated successfully, but these errors were encountered: