Skip to content

Some requests sent to global endpoint when using locational endpoint #15161

@scotthart

Description

@scotthart

In the C++ SDK, unless the AuthorityOption is set by the user, we default that value to the global endpoint. This was implemented before locational endpoints became widely used. It seems that this is probably not the best choice going forward.

Users are setting the EndpointOption to the locational value and expecting it to "just work" and it hasn't unless the lesser known AuthorityOption was also set to the hostname used in the EndpointOption.

The AuthorityOption should default to the EndpointOption hostname when the user sets the EndpointOption, simplifying configuration for when the user wants to use a locational endpoint. This would limit the use cases where the AuthorityOption needs to be set by the user to situations where they are connecting to an EAP or beta service.

Metadata

Metadata

Assignees

Labels

priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions