You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 26, 2024. It is now read-only.
We're seeing clients with a country determined by the LB but not a subdivision, which we fallback to "OK", causing bogus adM parameters of e.g. country-code=FR&subdivision=OK.
Instead let's pass adM an empty subdivision if one cannot be determined, their service seems ok with this instead of a bogus value.
We likely still want a fallback country (US) in case it could not be determined.
"adM prefers us to leave it empty other than leaving it out or sending incorrect values. e.g. if somehow we don't know about the region-code, they want this ...&country-code=US®ion-code=&"
We're seeing clients with a country determined by the LB but not a subdivision, which we fallback to "OK", causing bogus adM parameters of e.g.
country-code=FR&subdivision=OK
.Instead let's pass adM an empty subdivision if one cannot be determined, their service seems ok with this instead of a bogus value.
We likely still want a fallback country (US) in case it could not be determined.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: