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
On our multi-tenant system, separate tenants operate on separate domains. It's possible that such a domain might change one day - rendering all the links that might still "float around" invalid.
It might be useful to have the option to base the signature process on absolute URL or path only?
That seems reasonable. Actually, we could probably ALWAYS sign the path, not the full URL - I can't think of why the domain needs to be in the signature. But, for safety, an option is probably better (we could choose, in the future, to force that option to be set if we wanted to deprecate the old way).
On our multi-tenant system, separate tenants operate on separate domains. It's possible that such a domain might change one day - rendering all the links that might still "float around" invalid.
It might be useful to have the option to base the signature process on absolute URL or path only?
E.g., sign the URL https://foo.mycompany.com/do-something with the full URL (https://foo.mycompany.com) or the path only (/do-something).
We might be able to provide a PR if this seems useful for anybody else.
The text was updated successfully, but these errors were encountered: