Gitlab Pages 302 Redirect Header missing protocol
Summary
Stating a GET request to a Gitlab pages URL with an accept header of application/geo+json, application/json which is redirected using a 302 redirect misses the protocol in the response header.
Steps to reproduce
State a GET request e.g. to the URL https://situx.gitlab.io/deploytest/collections//LimesCoordinates_Kleinkastell//items?limit=10 and set the Accept header to application/geo+json, application/json
You can directly reproduce the behavior on this website: https://reqbin.com/qdat2lwg
The response header field "location" misses the protocoal HTTPS.
The error arose in the application QGIS when adding an OGC API Features service of the address:
https://situx.gitlab.io/deploytest/index.json
It allows to load FeatureCollections, but does not allow to download a FeatureCollection due to this error.
The equivalent project on Github allows the inclusion as OGC API Features:
https://situx.github.io/geostatdeploy/index.json
Example Project
https://gitlab.com/situx/deploytest
There is an equivalent project on Github, which does not exhibit this behavior.
https://github.com/situx/geostatdeploy/
What is the current bug behavior?
The location header of the 302 reply does not include the protocol e.g. https. Instead only // is given.
What is the expected correct behavior?
The location header should include https:// and not only //
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com but also in other Gitlab instances.