403 errors accessing https_git urls via tor

Users are receiving 403 errors when attempting to access git repos over HTTPS via tor

✔ ~
10:42 $ export https_proxy=http://localhost:8118
✔ ~
10:42 $ git ls-remote https://gitLAb.com/guardianproject/info
fatal: unable to access 'https://gitLAb.com/guardianproject/info/': The requested URL returned error: 403
✘-128 ~
10:42 $
✘-128 ~
10:42 $ git ls-remote https://gitLAb.com/guardianproject/info
fatal: unable to access 'https://gitLAb.com/guardianproject/info/': The requested URL returned error: 403
✘-128 ~
10:43 $ git ls-remote https://salsa.debian.org/freedombox-team/android-app.git
d5e6bb4e002a6c6837395708a65c4ee4271428ce        HEAD
d5e6bb4e002a6c6837395708a65c4ee4271428ce        refs/heads/master
3a8543ff4dd87461bd66ed710c1117c2cdc4274e        refs/heads/mvp
4b52abb460531dd58efb1cb1864f8b8131a24611        refs/merge-requests/22/head
5e4f75a8a721068286b8fd6c3e90e7efd20e1839        refs/merge-requests/23/head
2411f301cd5ed95da263176a1ce593160d9d372a        refs/merge-requests/24/head
b28b04b8e32a139c9635433b0f18f345f23647ae        refs/merge-requests/25/head
4e21249e88d95b337d5aba894f1fe716001044d6        refs/merge-requests/26/head
f451473900627136d83177f8e5f963b886c037cc        refs/merge-requests/27/head
9688ee9f0a9e72077efed7925377949fd76e21ab        refs/merge-requests/28/head
c89d365a98fa0338753b363cdc6d69b1950e0be1        refs/merge-requests/29/head
f2559ba45083c0e774a5f98afefc376efdc6d5e2        refs/merge-requests/30/head
2be019f665f7d22aecae0fa7df74bc7a97b5d39c        refs/merge-requests/31/head
e65a5dc57c0560f5ca4dc922ecb28637f411dd2c        refs/merge-requests/32/head
6e25c88fe5158d0163fd4e5a2c4b592a33a0b3d6        refs/merge-requests/33/head
fee6a0d8a31b9e23a2aed4009874fd4e9533c344        refs/merge-requests/34/head
b2462de6dfe5f8e5b026523d0e77d9ac686146f6        refs/merge-requests/35/head
1219c9989fc995711f93c3869cba517a887ed254        refs/merge-requests/36/head
8dda750a4e4099245f6bc9dd18d998ba80c158f8        refs/merge-requests/37/head
45e74a991e2dffe85236a65047509606cc385c2b        refs/merge-requests/38/head
4ba459f98a2848f9917591d1434fd59a64b4c08a        refs/merge-requests/39/head
d32989c2fb5d159dd32457d478a2b252cd3ecdd8        refs/merge-requests/40/head
6bb84c092545e62868369573a2e06dc348c4ce9e        refs/merge-requests/41/head
673ede13157f2d66e849ca426f00fc24aaf9d77b        refs/merge-requests/41/merge
e59552ceb2fa9baebe557b0a63952d7ac0f16580        refs/tags/v0.1
7373b6c2dc7b719aad13e174d9056a243ac54384        refs/tags/v0.2
73cf3a7c21abde3da30da43fdbe96d39ce46b8ac        refs/tags/v0.2^{}
7aeeb8b5bd1fa049cb46fbda8d022009e9bfce64        refs/tags/v0.3
bbee648bac5fe5a4814089e396c642c665b667d8        refs/tags/v0.3^{}
efce3907054d5ebf3eeab86e327d4be01afc3822        refs/tags/v0.4
c5f688f021e9528dfbf3ba2bafea6a69ab15d3a5        refs/tags/v0.4^{}
a759f4c67414b374cfeeed5388534cea9ce9496c        refs/tags/v0.5
c62ee3aba1b96a32df23cba9971ed3dbb18a26fd        refs/tags/v0.5^{}

The above test was run with a vanilla tor install, launched in the foreground via tor --HTTPTunnelPort 8118

This is in follow-up on the errors reported in https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/10212#note_354199502. While initially suspected of being related to the security settings on one of our page rules, further testing showed that even after disabling the rule, the errors still persisted.