Skip to content

Use proxied_site for geo proxied clone urls

What does this MR do and why?

From the comment here:

Currently, the code assumes if GEO_PROXIED_HEADER is 1, then GEO_PROXIED_EXTRA_DATA_HEADER is present and decoding it will succeed. We should instead go through with decoding the data and getting proxied_site in order to decide whether to use proxied_site here.

Use proxied_site instead of proxied_request to ensure that proxied site's decoding is successful.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #404497 (closed)

Edited by Mariia Solodovnik

Merge request reports