Customer-Supplied Encryption Key feature

There could be a problem by the customer-supplied encryption key feature in the current version 4.38, in the case you use IPv6 addresses. In the previous version 4.37 IPv6 addresses worked. The problem is that the IPv6 resolves a wrong country and the result of this is, that the service will cancel my request, even though I'm in the right country.

Can anybody confirm this ??

Start with issue #777 and compare the customer-supplied encryption key behavior between versions 4.37 and 4.38 using IPv6 addresses. Reproduce the reported country-resolution result and request cancellation, then document whether the regression is confirmed and what component is responsible.

Written by the indexing model from the issue text.