Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for ZKRoutingDataWriter to forward write requests as HTTPS as part of MetadataStoreRouting #2921

Open
GrantPSpencer opened this issue Sep 12, 2024 · 0 comments

Comments

@GrantPSpencer
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We do not allow HTTP write requests (PUT, POST, DELETE) to our helix-rest deployments. When a HTTPS write request is made to helix-rest on the RoutingData (aka modifying a sharding key), if the request does not hit the ZK_ROUTING_DATA_WRITER_LEADER, then it will forward the request to the leader but as an HTTP request.

The current workaround is to directly resolve the curl request to the host that is the current ZK_ROUTING_DATA_WRITER_LEADER so that the request is not forward.

Relevant methods:
buildAndSendRequestToLeader

addMetadataStoreRealm

deleteMetadataStoreRealm

addShardingKey

deleteShardingKey

Describe the solution you'd like
If possible, the ZKRoutingDataWriter should possibly support forwarding as HTTPS if the original request was also via HTTPS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant