Skip to content

REST: Add property for configuring user agent in http client #13234

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

singhpk234
Copy link
Contributor

@singhpk234 singhpk234 commented Jun 4, 2025

About the change

This change attempts to add UA so that clients can set this at their end and it can supplement the server for audit and debugging purpose, we do have X-Client-Version which helps solve most of the cases as this helps server understand that what version of the client the server is interacted, but in a world where we want to see the logs at server end and identify what happened to a client will be very hard.

Putting this change out to see if folks are interested in this !

Testing

Added a new UT

@github-actions github-actions bot added the core label Jun 4, 2025
@singhpk234 singhpk234 changed the title REST: Add UA REST: Add UA to IRC calls Jun 4, 2025
@amogh-jahagirdar amogh-jahagirdar changed the title REST: Add UA to IRC calls REST: Add property for configuring user agent in REST http client Jun 5, 2025
@@ -461,7 +466,8 @@ private static String addRequestTestCaseAndGetPath(HttpMethod method, Item body,
.withMethod(method.name().toUpperCase(Locale.ROOT))
.withHeader("Authorization", "Bearer " + BEARER_AUTH_TOKEN)
.withHeader(HTTPClient.CLIENT_VERSION_HEADER, icebergBuildFullVersion)
.withHeader(HTTPClient.CLIENT_GIT_COMMIT_SHORT_HEADER, icebergBuildGitCommitShort);
.withHeader(HTTPClient.CLIENT_GIT_COMMIT_SHORT_HEADER, icebergBuildGitCommitShort)
.withHeader(USER_AGENT, TEST_USER_AGENT);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just for my understanding, if I have a HTTP client configured to "my-user-agent" and then I later set it to "some-new-agent" on the request level, it will override it at the request level right? Just wanted to double check the order of precedence (not that I expect it to be used in practice that way)

Copy link
Contributor Author

@singhpk234 singhpk234 Jun 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

precisely, request level override always wins over the client level override.

@amogh-jahagirdar amogh-jahagirdar changed the title REST: Add property for configuring user agent in REST http client REST: Add property for configuring user agent in http client Jun 5, 2025
@@ -71,6 +71,8 @@ public class TestHTTPClient {

private static final int PORT = 1080;
private static final String BEARER_AUTH_TOKEN = "auth_token";
private static final String USER_AGENT = "User-Agent";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: USER_AGENT constant exists in HttpHeaders class.

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

Successfully merging this pull request may close these issues.

5 participants