Allow same URL to be usable for both machines-to-machine and users

[pierDipi]

Feature or Problem Description

The current UX is that the URL that is used to retrieve an artifact content in an application or CLI (API) is different from the one that is used by a human/user to visit / discover the schema (UI / studio).

I believe the UX would be better (and enable interesting schema discovery integrations) when the system automatically resolves a user / browser request and redirects the user to the UI / studio while the same URL can be used in applications or CLIs to retrieve the artifact content.

An example implementation that has this nice UX is GitHub container registry, when I visit for example ghcr.io/axllent/mailpit with a browser, GitHub redirects to the UI / webpage while at the same time podman pull works with the same URL podman pull ghcr.io/axllent/mailpit

Proposed Solution

TBD ...

Additional Context

[apicurio-bot]

Thank you for reporting an issue!

Pinging @andreaTP to respond or triage.

[EricWittmann]

Interesting feedback, thanks! I'll need to give this some thought. Not sure what the implementation of something like this would be. Features like this could be done as part of a docker compose package, with an nginx facade that could do interesting filtering like this.

[carlesarnal]

I think this is more a documentation request more than anything else. This should be possible already as Eric commented using nginx or some other reverse proxy (and do the filtering there based on e.g. user agent). I don't think this should be done at the project level.

[pierDipi]

I'm using the Operator and I couldn't find a way of doing that with the created OCP route