Lines Matching defs:server
19 * It is not meant to be used in a production server. Since it participates
36 * When you look at that location on your server, you will see a backtrace of
43 * Do NOT use this module on a production server. It attaches itself to every
44 * phase of the server runtime operations including startup, shutdown and
46 * negatively affect server performance.
92 * Sample configuration record. Used for both per-directory and per-server
101 * Note that while the per-directory and per-server configuration records are
109 * (directory, server, or combination).
124 * the server is (may be) multi-threaded.
274 /* server. */
293 * Locate our server configuration record for the specified server.
319 * sequence reported in the server's error_log, but beware - almost all of
342 * This utility routine traces the hooks called when the server starts up.
360 * that don't operate in a particular directory or server context. If we
361 * got a valid record, extract the location (directory or server) to which
399 example_log_each(r->pool, r->server, note);
529 trace_startup(cmd->pool, cmd->server, cfg, "cmd_example()");
535 * record. This will be called for the "default" server environment, and for
610 * If we're merging records for two different types of environment (server
628 * This function gets called to create a per-server configuration
629 * record. It will always be called for the "default" server.
658 * This function gets called to merge two per-server configuration
660 * the default server configuration The routine has the responsibility of
702 * the order in which the server calls them! See the command_rec *
734 * This routine is called before the server processes the configuration
749 * This routine is called after the server processes the configuration
753 * exits shortly after this phase) and once in the running server process.
756 * server will still call any remaining modules with an handler for this
793 * server will still call any remaining modules with an handler for this
807 * This routine is called after the server finishes the configuration
810 * this routine will be called only once, in the running server process.
813 * server will still call any remaining modules with an handler for this
836 * The arbitrary text we add to our trace entry indicates for which server
856 * The arbitrary text we add to our trace entry indicates for which server
893 * for a particular server. This is used for instance to omit the
944 /* Now we declare our content handlers, which are invoked when the server */
951 /* intervention by other parts of the server, they need to make */
1038 ap_rputs(" <STRONG>SVR()</STRONG> indicates a server environment\n", r);
1039 ap_rputs(" (blank means the main or default server, otherwise it's\n", r);
1076 * We did what we wanted to do, so tell the rest of the server we
1105 * This routine is called just after the server accepts the connection,
1108 * as soon as possible. The core server uses this phase to setup the
1177 * actual filename. If we don't do anything special, the server's default
1270 * If *all* modules return DECLINED, the request is aborted with a server
1317 * over and above the normal server things.
1353 static conn_rec *x_create_connection(apr_pool_t *p, server_rec *server,
1362 * This hook is defined in server/core.c, but it is not actually called
1419 /* Which functions are responsible for which hooks in the server. */
1518 /* the static hooks into our module from the other parts of the server. */
1530 x_create_server_config, /* server config creator */
1531 x_merge_server_config, /* server config merger */