Description
Problem
The v3 API's /ping endpoint has made a change to how versioning info is sent compared to v1 and v2, making those who have specific ways of parsing the endpoints adjust their process, which is unneeded effort on their end.
Desired Solution
We want to include versioning info in the Headers to make it a bit simpler for those migrating that need to do version comparisons; we'll also keep it in the body as well for continuity with current v3, and therefore we'll be keeping it a 200 instead of a 204.
Current v3 API /ping request response:
% curl -i http://localhost:8181/ping
HTTP/1.1 200 OK
date: Fri, 14 Mar 2025 15:04:40 GMT
{"version":"0.1.0","revision":"42117701c0"}%
Expected v3 API /ping request response:
% curl -i http://localhost:8181/ping
HTTP/1.1 200 OK
Content-Type: application/json
Transfer-Encoding: chunked
Request-Id: [generated-request-id]
X-Influxdb-Build: Core
X-Influxdb-Version: 0.1.0
X-Request-Id: [generated-request-id]
Date: Fri, 14 Mar 2025 15:04:40 GMT
{"version":"0.1.0","revision":"42117701c0"}