Delete button from Package Registry forwards to HTTP instead of HTTPS

Summary

Delete button on package registry does not work - accesses different control than from detailed view.

Steps to reproduce

When I open up the project page -> Packages & Registries -> Package Registry and I try to use the delete button (trash bin), it tells me

Something went wrong while deleting the package.

Example Project

What is the current bug behavior?

When I open up the project page -> Packages & Registries -> Package Registry and I try to use the delete button (trash bin), it tells me

Something went wrong while deleting the package.

While inspecting chrome network debug output, I noticed it is trying to call api (/api/v4/projects/ID/packages/ID) with http instead of https with status (blocked:mixed-content), if I try opening the api request using https, it returns the json well, but with http:// urls in the response.

What is the expected correct behavior?

Package will be deleted from Registry

Results of GitLab environment info

Docker GitLab 14.2.6 CE, docker image

Expand for output related to GitLab environment info 
System information
System:
Current User:   git
Using RVM:      no
Ruby Version:   2.7.2p137
Gem Version:    3.1.4
Bundler Version:2.1.4
Rake Version:   13.0.6
Redis Version:  6.0.16
Git Version:    2.32.0
Sidekiq Version:5.2.9
Go Version:     unknown

GitLab information
Version:        14.2.6
Revision:       9758b08ee05
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     12.7
URL:            http://REDACTED
HTTP Clone URL: http://REDACTED/some-group/some-project.git
SSH Clone URL:  ssh://git@REDACTED:2223/some-group/some-project.git
Using LDAP:     yes
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version:        13.19.1
Repository storage paths:
- default:      /opt/gitlab_data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell
Git:            /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab subtasks ...

Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 13.19.1 ? ... OK (13.19.1)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Gitaly ...


Gitaly: ... default ... OK


Checking Gitaly ... Finished


Checking Sidekiq ...


Sidekiq: ... Running? ... yes
Number of Sidekiq processes (cluster/worker) ... 1/1


Checking Sidekiq ... Finished


Checking Incoming Email ...


Incoming Email: ... Reply by email is disabled in config/gitlab.yml


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... Server: ldapmain
LDAP authentication... Failed. Check bind_dn and password configuration values
LDAP users with access to your GitLab server (only showing the first 100 results)
User output sanitized. Found 23 users of 100 limit.


Checking LDAP ... Finished


Checking GitLab App ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
1/1 ... yes
3/2 ... yes
3/3 ... yes
3/4 ... yes
3/5 ... yes
3/7 ... yes
8/8 ... yes
9/9 ... yes
9/11 ... yes
10/12 ... yes
11/13 ... yes
13/14 ... yes
13/15 ... yes
10/16 ... yes
10/17 ... yes
14/18 ... yes
14/19 ... yes
14/20 ... yes
14/21 ... yes
11/22 ... yes
11/24 ... yes
16/25 ... yes
16/26 ... yes
11/27 ... yes
16/28 ... yes
18/30 ... yes
5/31 ... yes
20/32 ... yes
10/33 ... yes
10/34 ... yes
22/36 ... yes
23/38 ... yes
23/39 ... yes
23/40 ... yes
23/41 ... yes
3/42 ... yes
22/43 ... yes
22/44 ... yes
22/45 ... yes
5/48 ... yes
5/49 ... yes
16/50 ... yes
10/55 ... yes
22/57 ... yes
14/61 ... yes
8/62 ... yes
14/63 ... yes
18/64 ... yes
33/65 ... yes
20/66 ... yes
11/67 ... yes
35/68 ... yes
38/69 ... yes
38/70 ... yes
38/71 ... yes
38/72 ... yes
14/73 ... yes
36/74 ... yes
35/75 ... yes
36/76 ... yes
36/77 ... yes
38/78 ... yes
14/79 ... yes
9/80 ... yes
14/81 ... yes
8/82 ... yes
35/83 ... yes
14/84 ... yes
14/85 ... yes
55/87 ... yes
Redis version >= 5.0.0? ... yes
Ruby version >= 2.7.2 ? ... yes (2.7.2)
Git version >= 2.31.0 ? ... yes (2.32.0)
Git user has default SSH configuration? ... yes
Active users: ... 18
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

Possible fixes

  1. Force API to return https while behind reverse proxy.
  2. Change the action on delete button to call method from package detail. I am now unable to delete packages unless I open package detail and press delete on that page (this calls /api/graphql). However this brings issue with packages without info - you cannot inspect those.
Edited by Hynek Bernard