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
The info page should know it has been called directly and now from redirection from /id/. We should either block (400 bad request) - or at least have a warning in the page stating that user might be trying to use this page as a persistent identifier.
The text was updated successfully, but these errors were encountered:
maybe.. the discussion here is what to do with people who use /info/ instead of /id/ (copy-pasted the link for instance). One option proposed is to have a sameAs relation between /id/ and /info/ but I want to test a way to at least warn users
The info page should know it has been called directly and now from redirection from /id/. We should either block (400 bad request) - or at least have a warning in the page stating that user might be trying to use this page as a persistent identifier.
The text was updated successfully, but these errors were encountered: