| /civetweb-2.7.6/ |
| D | RELEASE_NOTES.md | 8 - Support for flawed CGI interpreters returning only <LF> instead of <CR><LF>
9 - Add NO_FILESYSTEM flag for (embedded) system without any file system
10 - Several fixes for server side Lua scripts
11 - Disable SSL renegotiation for new OpenSSL version
14 - Fix some #include statements for various compilers / OS / SDK versions
15 - Support for Linux Standard Base (LSB)
20 - Fix include for Lua pages in "Kepler Syntax"
23 - Fixes for timeout handling
24 - Fixes for the request queue (rare loss of requests)
36 - Add API function to send file body for C and Lua
[all …]
|
| D | build.cmd | 32 @for %%a in (%options%) do @(
72 @for /f "skip=%log_keep%" %%f in ('dir /b /o-D /tc %log_folder%') do @(
126 @for %%m in (%methods%) do @(
145 @for %%a in (%*) do @echo.%%~a
161 :dependencies - Installs any prerequisites for the build
168 @call :log 0 "Installing dependencies for %generator%"
195 @call :log 0 "Generating CMake files for %generator%"
256 @call :log 0 "No build command for %generator%"
312 @for /f "tokens=1-3,*" %%a in ("%cmdcmdline%") do @(
348 @for /f "skip=2 tokens=2,*" %%a in ('reg query "%key%" /v "%var%"') do @set "arch=%%b"
[all …]
|
| /civetweb-2.7.6/docs/ |
| D | UserManual.md | 6 server. See `Embedding.md` for information on embedding CivetWeb into
23 For UNIX and Mac, CivetWeb does not detach from the terminal.
37 When started, CivetWeb first searches for the configuration file.
40 Otherwise, CivetWeb will search for the file `CivetWeb.conf` in the same directory that
56 For example: The above `CivetWeb.conf` file is used, and CivetWeb started as
89 CivetWeb uses shell-like glob patterns for several configuration options,
109 The following options are supported in `civetweb.c`. They can be used for
110 the stand-alone executable as well as for applications embedding CivetWeb.
112 The options are explained in alphabetic order - for a quick start, check
113 *document\_root*, *listening\_ports*, *error\_log\_file* and (for HTTPS) *ssl\_certificate*.
[all …]
|
| /civetweb-2.7.6/src/third_party/lua-5.1.5/ |
| D | HISTORY | 1 HISTORY for Lua 5.1
7 + new semantics for control variables of fors.
8 + new semantics for setn/getn.
9 + new syntax/semantics for varargs.
13 + metatables for all types
23 + better support for 64-bit machines.
24 + native loadlib support for Mac OS X.
39 + new generic for.
47 + more general syntax for function definition (e.g. function a.x.y:f()...end).
48 + more general syntax for function calls (e.g. (print or write)(9)).
[all …]
|
| /civetweb-2.7.6/src/third_party/duktape-1.5.2/config/ |
| D | genconfig.py | 7 # - option documentation for Duktape 1.x feature options (DUK_OPT_xxx)
8 # - option documentation for Duktape 1.x/2.x config options (DUK_USE_xxx)
16 # a reasonable starting point for manual duk_config.h tweaking.
18 # For Duktape 1.3 release the main goal was to autogenerate a Duktape 1.2
20 # being experimental. For Duktape 1.4 duk_config.h is always created from
95 # Preferred tag order for option documentation.
107 # Preferred tag order for generated C header files.
160 # but these are not a concrete issue for scanning preprocessor
180 re_line_requires = re.compile(r'(DUK_[A-Z0-9_]+)') # uppercase only, don't match DUK_USE_xxx for e…
183 provides = None # map from define to 'True' for now
[all …]
|
| /civetweb-2.7.6/src/third_party/duktape-1.8.0/config/ |
| D | genconfig.py | 7 # - option documentation for Duktape 1.x feature options (DUK_OPT_xxx)
8 # - option documentation for Duktape 1.x/2.x config options (DUK_USE_xxx)
16 # a reasonable starting point for manual duk_config.h tweaking.
18 # For Duktape 1.3 release the main goal was to autogenerate a Duktape 1.2
20 # being experimental. For Duktape 1.4 duk_config.h is always created from
95 # Preferred tag order for option documentation.
107 # Preferred tag order for generated C header files.
160 # but these are not a concrete issue for scanning preprocessor
180 re_line_requires = re.compile(r'(DUK_[A-Z0-9_]+)') # uppercase only, don't match DUK_USE_xxx for e…
183 provides = None # map from define to 'True' for now
[all …]
|
| /civetweb-2.7.6/src/third_party/lua-5.3.5/src/ |
| D | luaconf.h | 3 ** Configuration file for Lua
17 ** Search for "@@" to find all configurable definitions.
25 ** particular platform, for instance compiling it with 32-bit numbers or
51 #define LUA_USE_WINDOWS /* enable goodies for regular Windows */
56 #define LUA_DL_DLL /* enable support for DLL */
76 @@ LUA_C89_NUMBERS ensures that Lua uses the largest types available for
99 @@ LUA_INT_TYPE defines the type for Lua integers.
100 @@ LUA_FLOAT_TYPE defines the type for Lua floats.
103 ** and 'double' (the default), 32-bit integers and 'float' (for
104 ** restricted platforms), and 'long'/'double' (for C compilers not
[all …]
|
| /civetweb-2.7.6/src/third_party/duktape-1.8.0/src-separate/ |
| D | duk_hthread.h | 4 * duk_hthread is also the 'context' (duk_context) for exposed APIs
20 * always added to user-defined 'extra' for e.g. the
61 * Flags for __FILE__ / __LINE__ registered into tracedata
139 /* values for the state field */
148 * for reasonable execution timeout checking but large enough to keep
188 /* XXX: for a memory-code tradeoff, remove 'func' and make it's access either a function
192 /* Note: it's nice if size is 2^N (at least for 32-bit platforms). */
194 duk_tval tv_func; /* borrowed: full duk_tval for function being executed; for lightfuncs */
195 … /* borrowed: function being executed; for bound function calls, this is the final, real functi…
205 …* next instruction to execute (points to 'func' bytecode, stable pointer), NULL for native calls */
[all …]
|
| D | duk_bi_array.c | 6 * Array algorithms do not assume "magical" Array behavior for the "length"
7 * property, for instance.
9 * XXX: the "Throw" flag should be set for (almost?) all [[Put]] and
19 * correctly handled now (duk_uint32_t is not enough for all algorithms).
21 * For instance, push() can legitimately write entries beyond length 0xffffffff
30 * for compliance. When using "put" there may be inherited properties in
33 * check for this (for real world code, such side effects are very rare).
36 * binding) and "define" for setting values into a fresh result array.
51 /* Shared entry code for many Array built-ins. Note that length is left
110 for (i = 0; i < nargs; i++) { in duk_bi_array_constructor()
[all …]
|
| D | duk_js_compiler.c | 8 * The parser uses a traditional top-down recursive parsing for the
10 * for the expression level. The attempt is to minimize the C stack
20 * See doc/compiler.rst for discussion on the design.
24 * - duk_regconst_t: unsigned, no marker value for "none"
34 /* for array and object literals */
228 * Parser control values for tokens. The token table is ordered by the
231 * The binding powers are for lbp() use (i.e. for use in led() context).
232 * Binding powers are positive for typing convenience, and bits at the
233 * top should be reserved for flags. Binding power step must be higher
234 * than 1 so that binding power "lbp - 1" can be used for right associative
[all …]
|
| D | duk_heap.h | 5 * strings for one or more threads.
54 * Longjmp types, also double as identifying continuation type for a rethrow (in 'finally')
61 … 4 /* value1 -> label number, pseudo-type to indicate a break continuation (for ENDFIN) */
62 … 5 /* value1 -> label number, pseudo-type to indicate a continue continuation (for ENDFIN) */
63 … 6 /* value1 -> return value, pseudo-type to indicate a return continuation (for ENDFIN) */
64 …J_TYPE_NORMAL 7 /* no value, pseudo-type to indicate a normal continuation (for ENDFIN) */
77 … (1 << 3) /* don't run finalizers; leave finalizable objects in finalize_list for next round */
122 /* Stringcache is used for speeding up char-offset-to-byte-offset
123 * translations for non-ASCII strings.
191 * using the heap->heap_thread. This thread is also used for running
[all …]
|
| D | duk_numconv.c | 5 * a Dragon4 variant, with fast paths for small integers. Big integer
6 * arithmetic is needed for guaranteeing that the conversion is correct
23 * duk__str2num_digits_for_radix indicates, for each radix, how many input
24 * digits should be considered significant for string-to-number conversion.
28 * duk__str2num_exp_limits indicates, for each radix, the radix-specific
29 * minimum/maximum exponent values (for a Dragon4 integer mantissa)
63 * with the caller responsible for ensuring this is never exceeded. No memory
64 * allocation (except stack) is needed for bigint computation. Operations
65 * have been tailored for number conversion needs.
100 for (i = x->n - 1; i >= 0; i--) { in duk__bi_print()
[all …]
|
| D | duk_hobject_props.c | 4 * This is very central functionality for size, performance, and compliance.
5 * It is also rather intricate; see hobject-algorithms.rst for discussion on
6 * the algorithms and memory-management.rst for discussion on refcounts and
11 * - It might be tempting to assert "refcount nonzero" for objects
14 * (finalization) for instance. Hence, no refcount assertions are made.
25 * we're currently dealing with. For instance, the finalizer might
32 * - The order of operations for a DECREF matters. When DECREF is executed,
58 /* marker values for hash part */
62 /* valstack space that suffices for all local calls, including recursion
67 /* valstack space allocated especially for proxy lookup which does a
[all …]
|
| D | duk_regexp_compiler.c | 4 * See doc/regexp.rst for a discussion of the compilation approach and
16 * input string size (assuming an upper bound can be computed for number
40 /* Number of characters that the atom matches (e.g. 3 for 'abc'),
69 * larger than expected (or at least assert for it). Many things in the
82 /* XXX: return type should probably be duk_size_t, or explicit checks are needed for
113 /* special helper for emitting u16 lists (used for character ranges for built-in char classes) */
145 * variable length UTF-8 encoding. See doc/regexp.rst for discussion.
167 * duk_re_range_callback for generating character class ranges.
170 * We don't, for instance, eliminate duplicates or overlapping
178 * time execution time (see doc/regexp.rst for discussion).
[all …]
|
| /civetweb-2.7.6/src/third_party/duktape-1.5.2/src-separate/ |
| D | duk_hthread.h | 4 * duk_hthread is also the 'context' (duk_context) for exposed APIs
20 * always added to user-defined 'extra' for e.g. the
61 * Flags for __FILE__ / __LINE__ registered into tracedata
139 /* values for the state field */
148 * for reasonable execution timeout checking but large enough to keep
188 /* XXX: for a memory-code tradeoff, remove 'func' and make it's access either a function
192 /* Note: it's nice if size is 2^N (at least for 32-bit platforms). */
194 duk_tval tv_func; /* borrowed: full duk_tval for function being executed; for lightfuncs */
195 … /* borrowed: function being executed; for bound function calls, this is the final, real functi…
205 …* next instruction to execute (points to 'func' bytecode, stable pointer), NULL for native calls */
[all …]
|
| D | duk_bi_array.c | 6 * Array algorithms do not assume "magical" Array behavior for the "length"
7 * property, for instance.
9 * XXX: the "Throw" flag should be set for (almost?) all [[Put]] and
19 * correctly handled now (duk_uint32_t is not enough for all algorithms).
21 * For instance, push() can legitimately write entries beyond length 0xffffffff
30 * for compliance. When using "put" there may be inherited properties in
33 * check for this (for real world code, such side effects are very rare).
36 * binding) and "define" for setting values into a fresh result array.
51 /* Shared entry code for many Array built-ins. Note that length is left
110 for (i = 0; i < nargs; i++) { in duk_bi_array_constructor()
[all …]
|
| D | duk_js_compiler.c | 8 * The parser uses a traditional top-down recursive parsing for the
10 * for the expression level. The attempt is to minimize the C stack
20 * See doc/compiler.rst for discussion on the design.
24 * - duk_regconst_t: unsigned, no marker value for "none"
34 /* for array and object literals */
228 * Parser control values for tokens. The token table is ordered by the
231 * The binding powers are for lbp() use (i.e. for use in led() context).
232 * Binding powers are positive for typing convenience, and bits at the
233 * top should be reserved for flags. Binding power step must be higher
234 * than 1 so that binding power "lbp - 1" can be used for right associative
[all …]
|
| D | duk_heap.h | 5 * strings for one or more threads.
54 * Longjmp types, also double as identifying continuation type for a rethrow (in 'finally')
61 … 4 /* value1 -> label number, pseudo-type to indicate a break continuation (for ENDFIN) */
62 … 5 /* value1 -> label number, pseudo-type to indicate a continue continuation (for ENDFIN) */
63 … 6 /* value1 -> return value, pseudo-type to indicate a return continuation (for ENDFIN) */
64 …J_TYPE_NORMAL 7 /* no value, pseudo-type to indicate a normal continuation (for ENDFIN) */
77 … (1 << 3) /* don't run finalizers; leave finalizable objects in finalize_list for next round */
122 /* Stringcache is used for speeding up char-offset-to-byte-offset
123 * translations for non-ASCII strings.
191 * using the heap->heap_thread. This thread is also used for running
[all …]
|
| D | duk_numconv.c | 5 * a Dragon4 variant, with fast paths for small integers. Big integer
6 * arithmetic is needed for guaranteeing that the conversion is correct
23 * duk__str2num_digits_for_radix indicates, for each radix, how many input
24 * digits should be considered significant for string-to-number conversion.
28 * duk__str2num_exp_limits indicates, for each radix, the radix-specific
29 * minimum/maximum exponent values (for a Dragon4 integer mantissa)
63 * with the caller responsible for ensuring this is never exceeded. No memory
64 * allocation (except stack) is needed for bigint computation. Operations
65 * have been tailored for number conversion needs.
100 for (i = x->n - 1; i >= 0; i--) { in duk__bi_print()
[all …]
|
| D | duk_hobject_props.c | 4 * This is very central functionality for size, performance, and compliance.
5 * It is also rather intricate; see hobject-algorithms.rst for discussion on
6 * the algorithms and memory-management.rst for discussion on refcounts and
11 * - It might be tempting to assert "refcount nonzero" for objects
14 * (finalization) for instance. Hence, no refcount assertions are made.
25 * we're currently dealing with. For instance, the finalizer might
32 * - The order of operations for a DECREF matters. When DECREF is executed,
58 /* marker values for hash part */
62 /* valstack space that suffices for all local calls, including recursion
67 /* valstack space allocated especially for proxy lookup which does a
[all …]
|
| D | duk_regexp_compiler.c | 4 * See doc/regexp.rst for a discussion of the compilation approach and
16 * input string size (assuming an upper bound can be computed for number
40 /* Number of characters that the atom matches (e.g. 3 for 'abc'),
69 * larger than expected (or at least assert for it). Many things in the
82 /* XXX: return type should probably be duk_size_t, or explicit checks are needed for
113 /* special helper for emitting u16 lists (used for character ranges for built-in char classes) */
145 * variable length UTF-8 encoding. See doc/regexp.rst for discussion.
167 * duk_re_range_callback for generating character class ranges.
170 * We don't, for instance, eliminate duplicates or overlapping
178 * time execution time (see doc/regexp.rst for discussion).
[all …]
|
| /civetweb-2.7.6/src/third_party/ |
| D | sqlite3.h | 8 ** May you find forgiveness for yourself and forgive others.
24 ** The official C-language API documentation for SQLite is derived
35 #include <stdarg.h> /* Needed for the definition of va_list */
73 ** should not use deprecated interfaces - they are supported for backwards
101 ** format "X.Y.Z" where X is the major version number (always 3 for
106 ** The SQLITE_VERSION_NUMBER for any given release of SQLite will also
149 ** function is provided for use in DLLs since DLL users usually do not have
178 ** ^Support for the diagnostic functions sqlite3_compileoption_used()
206 ** the mutexes. But for maximum safety, mutexes should be enabled.
207 ** ^The default behavior is for mutexes to be enabled.
[all …]
|
| /civetweb-2.7.6/src/third_party/lua-5.2.4/doc/ |
| D | readme.html | 90 The instructions given below for building Lua are for Unix-like platforms.
92 <A HREF="#other">instructions for other systems</A>
190 These are the only directories you need for development.
193 The files in <TT>include</TT> and <TT>lib</TT> are needed for
220 This is done automatically for all platforms listed above that have
221 this feature and also for Windows.
226 If you're not using the usual Unix tools, then the instructions for
228 projects (or whatever your compiler uses) for building the library,
253 C libraries for Lua you'll need to know how to create dynamic libraries
256 into each dynamic library. For Unix, we recommend that the Lua library
[all …]
|
| /civetweb-2.7.6/include/ |
| D | civetweb.h | 16 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
17 * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
64 /* SSL is still often used synonymously for TLS. */
89 /* Provide data required for caching files. */
111 * features: bit mask for features to be initialized.
131 struct mg_context; /* Handle for the HTTP service itself */
132 struct mg_connection; /* Handle for the individual connection */
218 which callbacks to invoke. For a detailed description, see
233 return code is stored as a HTTP status code for the
280 connection is ready for data exchange.
[all …]
|
| /civetweb-2.7.6/src/third_party/lua-5.2.4/src/ |
| D | luaconf.h | 3 ** Configuration file for Lua
17 ** Search for "@@" to find all configurable definitions.
33 #define LUA_WIN /* enable goodies for regular Windows platforms */
49 #define LUA_USE_LONGLONG /* assume support for long long */
58 #define LUA_USE_LONGLONG /* assume support for long long */
79 @@ LUA_PATH_DEFAULT is the default path that Lua uses to look for
81 @@ LUA_CPATH_DEFAULT is the default path that Lua uses to look for
115 @@ LUA_DIRSEP is the directory separator (for submodules).
135 @@ LUA_API is a mark for all core API functions.
136 @@ LUALIB_API is a mark for all auxiliary library functions.
[all …]
|
