Url for the next request with pagination is missing port

Summary

Url for the next request with pagination is missing port between version gitlab-ee:11.8.1-ee.0 and gitlab-ee:11.11.0-ee.0

More details are given here

In my case I had a python script using python-gitlab library. Everything was ok with gitlab-ee:11.8.1-ee.0. Then I used new docker image gitlab-ee:11.11.0-ee.0 and it has started to fail.

I have run the curl command given into the link above on a gitlab-ee:11.8.1-ee.0 and gitlab-ee:11.11.0-ee.0, and indeed link attribute has changed. With gitlab-ee:11.11.0-ee.0 the correct port to use has disappeared.

Steps to reproduce

have two Gitlab instances, one (host1) with version 11.8.1-ee.0, the other (host2) with version 11.11.0-ee.0. Those instances must use a different port than 443 for https
choose on host 1 and 2 a user with API token
Run on the two hosts the following curl command

curl --insecure --header "PRIVATE-TOKEN: <MyToken>" "https://<MyHost>:<configuredHttpsPort>/api/v4/projects" -sSL -D - -o /dev/null

link attribute returned between gitlab-ee:11.8.1-ee.0 and gitlab-ee:11.11.0-ee.0 is different. In the case of gitlab-ee:11.8.1-ee.0 with the FQDN and port (which is the expected behavior), in the case of gitlab-ee:11.11.0-ee.0 FQDN information is available but not the port

Example Project

Running the curl command on Gitlab.com give no https port information, but seems normal since on Gitlab.com it is the classical https port which is used.

What is the current bug behavior?

link attribute returned between gitlab-ee:11.8.1-ee.0 and gitlab-ee:11.11.0-ee.0 is different. In the case of gitlab-ee:11.8.1-ee.0 with the FQDN and port (which is the expected behavior), in the case of gitlab-ee:11.11.0-ee.0 FQDN information is available but not the port

What is the expected correct behavior?

Into the link attribute returned by the curl command FQDN and port must be available

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

On gitlab-ee:11.8.1-ee.0 instance

root@gitlab2:/# gitlab-rake gitlab:env:info

System information
System:		
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.5.3p105
Gem Version:	2.7.6
Bundler Version:1.16.6
Rake Version:	12.3.2
Redis Version:	3.2.12
Git Version:	2.18.1
Sidekiq Version:5.2.5
Go Version:	unknown

GitLab information
Version:	11.8.1-ee
Revision:	39d0b2e
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
DB Version:	9.6.11
URL:		https://<myFQDN>:<myHttpsPort>
HTTP Clone URL:	https://<myFQDN>:<myHttpsPort>/some-group/some-project.git
SSH Clone URL:	ssh://git@<myFQDN>:<mySshPort>/some-group/some-project.git
Elasticsearch:	no
Geo:		no
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers: 

GitLab Shell
Version:	8.4.4
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
Hooks:		/opt/gitlab/embedded/service/gitlab-shell/hooks
Git:		/opt/gitlab/embedded/bin/git

On gitlab-ee:11.11.0-ee.0 instance

root@gitlab:/# gitlab-rake gitlab:env:info

System information
System:		
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.5.3p105
Gem Version:	2.7.9
Bundler Version:1.17.3
Rake Version:	12.3.2
Redis Version:	3.2.12
Git Version:	2.21.0
Sidekiq Version:5.2.7
Go Version:	unknown

GitLab information
Version:	11.11.0-ee
Revision:	deb6f84e91f
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	9.6.11
URL:		https://<myFQDN>:<myHttpsPort>
HTTP Clone URL:	https://<myFQDN>:<myHttpsPort>/some-group/some-project.git
SSH Clone URL:	ssh://git@<myFQDN>:<mySshPort>/some-group/some-project.git
Elasticsearch:	no
Geo:		no
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers: 

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

Results of GitLab application Check