Lines Matching +full:- +full:- +full:no +full:- +full:check +full:- +full:certificate

8 | :--- | :--- |
10 …equest()` is called before any authorization is done. If an authorization check is required, `requ…
12 …-context mutex is locked when the callback function is invoked. The function is primarily useful f…
18 …eturn 1 to signal CivetWeb that no further processing is needed. If the returned value is 0, Civet…
24 … setup and no further processing is necessary. Also with a return value of 1 another callback func…
26 …certificate. With a return value of 1 the callback function signals CivetWeb that the certificate …
29 | |**0** - The master thread is created |
30 | |**1** - A worker thread which handles client connections has been created|
31 | |**2** - An internal helper thread (timer thread) has been created|
36 …nes to log the access. If a non-zero value is returned, CivetWeb assumes that access logging has a…
38 …utines to log the message. If a non-zero value is returned CivetWeb assumes that logging has alrea…
45 | |**0** - CivetWeb can proceed with the handshake to accept the connection |
46 | |**1** - CivetWeb must close the connection immediately without performing a handshake |
49 | | **`bits`** - The first byte of the websocket frame. See [RFC-6455](http://tools.ietf.org/html/r…
50 | | **`data`** - The pointer to the received data block. Masks--if any--have already been applied. |
51 | | **`data_len`** - The length of the received data block |
52 …by the callback function, CivetWeb will close the websocket connection and no more frames will be …