You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
It is strongly recommended to add a link with relation type canonical, which points to this STAC document using a signed URL.
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:
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.
(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: