Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI support for Citation of Canonical URIs #95

Open
rob-metalinkage opened this issue Apr 20, 2021 · 2 comments
Open

UI support for Citation of Canonical URIs #95

rob-metalinkage opened this issue Apr 20, 2021 · 2 comments
Assignees
Labels
Definitions Server enhancement New feature or request UI upgrade needed Needs update to UI rendering toolkit

Comments

@rob-metalinkage
Copy link
Contributor

Need to make the expectation that only canonical URIs are bookmarkable meaningfully much more visible.

Keep a weather eye open for clever options - only invasive browser plugins seem to offer this however so its a UI problem.

This is a live issue for VocPrez RDFLib/VocPrez#36

@rob-metalinkage rob-metalinkage added enhancement New feature or request UI upgrade needed Needs update to UI rendering toolkit Definitions Server labels Apr 20, 2021
@rob-metalinkage rob-metalinkage self-assigned this Apr 20, 2021
@rob-metalinkage
Copy link
Contributor Author

is http 302 the answer?

https://airbrake.io/blog/http-errors/303-see-other

todo: experiment with browser behaviour.

@jerstlouis
Copy link
Member

jerstlouis commented Jun 4, 2021

My 2 cents: content negotiation / negotiation by profile & 200 is the answer, whenever possible ;)

As far as I understand, the difference between 302 and 303 is that "HTTP/1.1 added the new status codes 303 and 307 to disambiguate between the two behaviours, with 303 mandating the change of request type to GET, and 307 preserving the request type as originally sent". ( https://en.wikipedia.org/wiki/HTTP_302 )

So I don't exect browsers would behave any differently with a 302 resulting from a GET than with a 303 and will still show the location redirected to in the address bar / bookmarks.

I just tested that and that is definitely the case with Chromium:
302 still updates the address bar to the location redirected to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Definitions Server enhancement New feature or request UI upgrade needed Needs update to UI rendering toolkit
Projects
None yet
Development

No branches or pull requests

2 participants