search

opengeospatial / NamingAuthority

Primary repo for the OGC Naming Authority
6 stars 12 forks source link

UI support for Citation of Canonical URIs #95

Open rob-metalinkage opened 3 years ago

rob-metalinkage commented 3 years ago

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 https://github.com/RDFLib/VocPrez/issues/36

rob-metalinkage commented 3 years ago

is http 302 the answer?

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

todo: experiment with browser behaviour.

jerstlouis commented 3 years ago

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.