Use HTTP keep-alive #137

New Issue

2026-10-05T04:00:51+02:00

adam commented

2026-10-05 04:00:51 +02:00

Current code doesn't allow to do interesting stuff, because every HTTP request is parsed only from beginning of the connection.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/650-use-http-keep-alive?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Current code doesn't allow to do interesting stuff, because every HTTP request is parsed only from beginning of the connection. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/650-use-http-keep-alive?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam commented

2026-10-05 04:00:52 +02:00

Define "interesting stuff", please (and how keep-alive helps with it)

Define "interesting stuff", please (and how keep-alive helps with it)

adam commented

2026-10-05 04:00:53 +02:00

I want a module to use long polling for its web needs.
If to use OnWebPreRequest and send Connection: keep-alive myself without closing the socket, browser will see the open socket, and will send through it not only request related to the module, but to the whole ZNC.

Also there's no good way to read from the socket, which wasn't closed via returning true from OnWebPreRequest(), because ZNC is event-driven, and such socket doesn't notify my module about new data.

Moving support for keep-alive to core would help, it'll just do OnWebRequest() on the module not only on new connections, but on old ones too.

I want a module to use long polling for its web needs. If to use OnWebPreRequest and send Connection: keep-alive myself without closing the socket, browser will see the open socket, and will send through it not only request related to the module, but to the whole ZNC. Also there's no good way to read from the socket, which wasn't closed via returning true from OnWebPreRequest(), because ZNC is event-driven, and such socket doesn't notify my module about new data. Moving support for keep-alive to core would help, it'll just do OnWebRequest() on the module not only on new connections, but on old ones too.

adam commented

2026-10-05 04:00:54 +02:00

Even if it's not real "long polling"...

Even if it's not real "long polling"...

adam commented

2026-10-05 04:00:54 +02:00

How about this: Return true from OnWebPreRequest() and use the socket manager's SwapSockByAddr() to replace the HTTP socket with your own code.

How about this: Return true from OnWebPreRequest() and use the socket manager's SwapSockByAddr() to replace the HTTP socket with your own code.

adam commented

2026-10-05 04:00:55 +02:00

It doesn't stop browser to do requests via this connection unrelated to my module.
Browsers don't know that this connection is only for that ZNC module, they just see site name.

It doesn't stop browser to do requests via this connection unrelated to my module. Browsers don't know that this connection is only for that ZNC module, they just see site name.

adam commented

2026-10-05 04:00:56 +02:00

Uhm, just don't send back a keep-alive header. Just "replying slowly" should already work fine, shouldnt it?

Uhm, just don't send back a keep-alive header. Just "replying slowly" should already work fine, shouldnt it?

adam commented

2026-10-05 04:00:56 +02:00

dd576a0ccdf625c2df806a2e43cead1c60d41dae

dd576a0ccdf625c2df806a2e43cead1c60d41dae

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#137