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 }}
Repository navigation
[Feature] Correlate Java SDK HTTP requests with server request contextΒ #15900
Is your feature request related to a problem? Please describe.
Java SDK gRPC requests carry a request ID, but SDK HTTP requests do not consistently carry one. The server consequently generates its own HTTP request-context ID, preventing callers and server-side request context from sharing a correlation ID.
Describe the solution you would like
Generate a fresh UUID in Nacos-Request-Id for every SDK HTTP request execution, covering the shared, Config, and Naming HTTP clients and AI requests that reuse them. Keep caller-owned headers, client identity, module metadata, and the legacy RequestId header unchanged.
The server should copy a non-blank Nacos-Request-Id into RequestContext.requestId, retain its generated UUID for missing or blank headers, and clear the context after both successful and failed requests. Existing gRPC behavior and compatibility with older clients and servers should remain intact.
Describe alternatives you have considered
Adding IDs independently in each domain proxy duplicates transport behavior and can miss retry or polling paths. Injecting the header in the SDK HTTP client factories provides common coverage.
Additional context
The ID is correlation metadata, not an authentication credential or an idempotency key. No response echo or new diagnostic endpoint is required. The client transport and server request-context specifications should document the behavior together.
Activity
For #15900, correlate SDK HTTP requests with server context (#15901)
[ISSUE #15799] Sync develop into summer-ospp#15799 (#15937)