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
Hi, I use this docker registry UI and I have an issue.
I am using the proxy scenario, to avoid cors/mixed content/authentication/etc issues.
Bug description
If I access the ui as:
https://myserver.test/registry-ui/
it works fine.
If instead I access:
https://myserver.test/registry-ui/index.html
the GUI shows up, but complains as "Server not found", since it tries to access https://myserver.test/registry-ui/index.html/v2/_catalog?n=100000 instead of https://myserver.test/registry-ui/v2/_catalog?n=100000.
How to Reproduce
Probably using one of this project examples of the proxy scenario suffices.
Expected behavior
To access the registry. Basically, the request should "strip" index.html from the url.
System information
Using this project official docker image, v 2.0.1
The text was updated successfully, but these errors were encountered:
Hi, I use this docker registry UI and I have an issue.
I am using the proxy scenario, to avoid cors/mixed content/authentication/etc issues.
Bug description
If I access the ui as:
it works fine.
If instead I access:
the GUI shows up, but complains as "Server not found", since it tries to access
https://myserver.test/registry-ui/index.html/v2/_catalog?n=100000
instead ofhttps://myserver.test/registry-ui/v2/_catalog?n=100000
.How to Reproduce
Probably using one of this project examples of the proxy scenario suffices.
Expected behavior
To access the registry. Basically, the request should "strip"
index.html
from the url.System information
Using this project official docker image, v 2.0.1
The text was updated successfully, but these errors were encountered: