BUG/MEDIUM: cli: Be sure to catch immediate client abort
A client abort while nothing was sent is properly handled except when this immediately happens after the connection was accepted. The read0 event is caught before the CLI applet is created. In that case, the shutdown is not handled and the applet is no longer wakeup. In that case, the stream remains blocked and no timeout are armed. The bug was due to the fact that when the applet I/O handler was called for the first time, the applet context was initialized and nothing more was performed. A shutdown, if any, would be handled on the next call. In that case, it was too late. Now, afet the init step, we loop to eval the first command. There is no command here but the shutdown will be tested. This patch should fix the issue #2727. It must be backported to 3.0.
This commit is contained in:
parent
d622f9d5b6
commit
14a413033c
|
@ -1070,7 +1070,6 @@ static void cli_io_handler(struct appctx *appctx)
|
||||||
if (appctx->st0 == CLI_ST_INIT) {
|
if (appctx->st0 == CLI_ST_INIT) {
|
||||||
/* reset severity to default at init */
|
/* reset severity to default at init */
|
||||||
cli_init(appctx);
|
cli_init(appctx);
|
||||||
break;
|
|
||||||
}
|
}
|
||||||
else if (appctx->st0 == CLI_ST_END) {
|
else if (appctx->st0 == CLI_ST_END) {
|
||||||
applet_set_eos(appctx);
|
applet_set_eos(appctx);
|
||||||
|
|
Loading…
Reference in New Issue