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
When annotating PDFs in Via, the URL that is recorded with the annotation (ie. its target_uri property in the h backend) reflects the URL that was initially passed to Via, not the actual URL that the PDF was fetched from after following any redirects. This means that users annotating the same PDF via different links which all redirect to the same location can end up creating annotations associated with different URLs. This issue also means that the URL associated with a document can be different for one user who annotates it through Via and another user who annotates via the Chrome extension.
From a practical point of view this tends not to matter because the PDF fingerprint will be the same in both cases, any links to the document from activity pages etc. will still work as long as the site owner has the redirect in place.
When annotating PDFs in Via, the URL that is recorded with the annotation (ie. its
target_uri
property in the h backend) reflects the URL that was initially passed to Via, not the actual URL that the PDF was fetched from after following any redirects. This means that users annotating the same PDF via different links which all redirect to the same location can end up creating annotations associated with different URLs. This issue also means that the URL associated with a document can be different for one user who annotates it through Via and another user who annotates via the Chrome extension.From a practical point of view this tends not to matter because the PDF fingerprint will be the same in both cases, any links to the document from activity pages etc. will still work as long as the site owner has the redirect in place.
While it is generally true that we would want the annotation's URL to reflect the final URL, there are some cases where we might not want to do that. For example, if a stable URL redirects to a temporary URL. This can happen with Google Drive PDF download URLs (used in the LMS app) for example (https://drive.google.com/uc?id={id}&export=download is a stable URL that redirects to a temporary signed URL like https://doc-0s-90-docs.googleusercontent.com/docs/securesc/{long_signature}).
Steps to reproduce:
Expected result:
The annotation's URL should reflect the final location that the PDF was fetched from, after following redirects.
Actual result:
The annotation's URL reflects the initial location that the PDF was requested from. eg. https://arxiv.org/pdf/2105.01649 rather than https://arxiv.org/pdf/2105.01649.pdf
The text was updated successfully, but these errors were encountered: