404 in UI when publishing container image with a slash in name about gitea HOT 4 CLOSED

• Open web UI. Navigate to Profile -> Packages. You should see the pushed image with the name namespace/name.
• Click on the said image.

What URL do you see? Could you copy out the original link to see whether it is a/b or a%2fb ?

from gitea.

What URL do you see? Could you copy out the original link to see whether it is a/b or a%2fb ?

When I click on a container in package list (name label is namespace/name), the URL is as follows: http://gitea.example.com/username/-/packages/container/namespace%2Fname/latest. So, with %2F. This page is 404.

from gitea.

If you access the URL with %2F directly, what does Gitea side see (the Gitea logs) ? If Gitea also sees %2F, then it is a Gitea's bug. If Gitea only sees /, then it is the reverse proxy's problem: it shouldn't decode the path.

from gitea.

If you access the URL with %2F directly, what does Gitea side see (the Gitea logs) ? If Gitea also sees %2F, then it is a Gitea's bug. If Gitea only sees /, then it is the reverse proxy's problem: it shouldn't decode the path.

Gitea sees /. And it is, apparently, a reverse proxy problem, as I am running Gitea behind an NGINX proxy.

I confirm that without NGINX reverse proxy, the issue does not reproduce.

I investigated the issue and managed to find a solution. It was incorrect reverse proxy configuration.

I had reverse proxy of NGINX configured as follows (unrelated directives are omitted for clarity):

location / {
    proxy_pass http://127.0.0.1:3000/;
}

Removing the trailing slash in proxy_pass directive fixed the issue.

location / {
    proxy_pass http://127.0.0.1:3000;
}

I also noticed that the correct configuration is also outlined in documentation.

@wxiaoguang Thank you for helping to figure this out! It was my mistake in the end.

from gitea.