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
When hosting under a subpath behind a reverse proxy (say, http://myserver.local/gitea as ROOT_URL), button "Clean up expired artifacts" in Site Administration->Code Assets->Packages (/admin/packages) does not work, resulting in a 404 instead.
The button POSTs to /admin/packages/cleanup, while expected to POST to /gitea/admin/packages/cleanup, where /gitea prefix is the subpath Gitea is being hosted on. If I manually add the subpath prefix to HTML via browser inspector, the button works, like this: <form method="post" action="/gitea/admin/packages/cleanup">
This seems to be due to missing usage of AppSubUrlhere, like its used in otherplaces.
Gitea Version
1.12.10
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Systemd
Database
None
The text was updated successfully, but these errors were encountered:
Description
When hosting under a subpath behind a reverse proxy (say,
http://myserver.local/gitea
as ROOT_URL), button "Clean up expired artifacts" in Site Administration->Code Assets->Packages (/admin/packages
) does not work, resulting in a 404 instead.The button POSTs to
/admin/packages/cleanup
, while expected to POST to/gitea/admin/packages/cleanup
, where/gitea
prefix is the subpath Gitea is being hosted on. If I manually add the subpath prefix to HTML via browser inspector, the button works, like this:<form method="post" action="/gitea/admin/packages/cleanup">
This seems to be due to missing usage of
AppSubUrl
here, like its used in other places.Gitea Version
1.12.10
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Systemd
Database
None
The text was updated successfully, but these errors were encountered: