Call to `/status` to ensure it is valid rqlite node

[invisal]

If you can, I would perform an explicit "network test connect" call first. Call /status, and ensure you get 200 back. That way you can be sure you're talking to an rqlite node.

Actually it just calls the URL and looks for X-Rqlite-Version has a HTTP header in the response.

Reference:
https://github.com/rqlite/rqlite/blob/master/cmd/rqlite/main.go#L101

[otoolep]

Actually, just call / on whatever host and port is supplied in the URL. See:

~ $ curl -v localhost:4001
*   Trying ::1:4001...
* TCP_NODELAY set
* Connected to localhost (::1) port 4001 (#0)
> GET / HTTP/1.1
> Host: localhost:4001
> User-Agent: curl/7.68.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 302 Found
< Access-Control-Allow-Credentials: true
< Access-Control-Allow-Headers: Content-Type, Authorization
< Access-Control-Allow-Methods: OPTIONS, GET, POST
< Content-Type: text/html; charset=utf-8
< Location: /status
< X-Rqlite-Version: v8.23.0
< Date: Fri, 29 Mar 2024 13:21:44 GMT
< Content-Length: 30
< 
<a href="/status">Found</a>.

* Connection #0 to host localhost left intact
~ $ 

Then look for X-Rqlite-Version as a header (value doesn't matter, just that it's there).

[doublesilver]

/attempt #59

[doublesilver]

/attempt #59

[doublesilver]

/attempt #59