> For the complete documentation index, see [llms.txt](https://node1.gitbook.io/node1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node1.gitbook.io/node1-docs/solana/fast-landing/keep-alive.md). # Keep-alive connections ## Keep-Alive Requirement node1 is designed to work best with persistent HTTP connections (HTTP Keep-Alive). Clients are expected to maintain Keep-Alive connections when communicating with the service to ensure optimal performance and stability. * Eliminates repeated TCP/TLS handshakes. * Significantly reduces end-to-end latency for frequent requests. * Improves performance under sustained or bursty traffic. ## How to Keep the Connection Alive Most HTTP/1.1 clients enable Keep-Alive by default, but some custom implementations or proxies may disable it. Please ensure your client is configured to keep connections open. ### 1. Ensure HTTP/1.1 Usage For HTTP/1.1, Keep-Alive is enabled by default. If you manage headers manually, do not send "Connection: close". ### 2. Use Ping Endpoint Use the GET /ping endpoint as a lightweight health check to confirm connectivity. * Method: `GET` * Path: `/ping` * Response: `pong` * Status: `200 OK` ## Example (curl) Test connectivity: ```bash curl -s http://ny.node1.me/ping # Output: pong ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://node1.gitbook.io/node1-docs/solana/fast-landing/keep-alive.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.