Good catch! Seems indeed important to ensure that the signing logic (and the underlying provider) supports this use case, seeing as it's probably the default one for signed URLs, as pointed out by @andrewgaul