diff options
Diffstat (limited to 'docs/manual/developer/new_api_2_4.html.en')
| -rw-r--r-- | docs/manual/developer/new_api_2_4.html.en | 52 |
1 files changed, 26 insertions, 26 deletions
diff --git a/docs/manual/developer/new_api_2_4.html.en b/docs/manual/developer/new_api_2_4.html.en index 3e0050e..db40eb8 100644 --- a/docs/manual/developer/new_api_2_4.html.en +++ b/docs/manual/developer/new_api_2_4.html.en @@ -1,7 +1,7 @@ -<?xml version="1.0" encoding="ISO-8859-1"?> +<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head> -<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" /> +<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT @@ -30,7 +30,7 @@ version 2.2 to 2.4, that may be of interest to module/application developers and core hacks. As of the first GA release of the 2.4 branch API compatibility is preserved for the life of the - 2.4 branch. (The + 2.4 branch. (The <a href="http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/VERSIONING">VERSIONING</a> description for the 2.4 release provides more information about API compatibility.)</p> @@ -119,9 +119,9 @@ <li>New API to retain data across module unload/load</li> <li>New <code>check_config</code> hook</li> <li>New <code>ap_process_fnmatch_configs()</code> function to process wildcards</li> - <li>Change <code>ap_configfile_t</code>, <code>ap_cfg_getline()</code>, - <code>ap_cfg_getc()</code> to return error codes, and add - <code>ap_pcfg_strerror()</code> for retrieving an error description.</li> + <li>Change <code>ap_configfile_t</code>, <code>ap_cfg_getline()</code>, + <code>ap_cfg_getc()</code> to return error codes, and add + <code>ap_pcfg_strerror()</code> for retrieving an error description.</li> <li>Any config directive permitted in ACCESS_CONF context must now correctly handle being called from an .htaccess file via the new <code class="directive"><a href="../mod/core.html#allowoverridelist">AllowOverrideList</a></code> directive. @@ -133,7 +133,7 @@ <h3><a name="http_core" id="http_core">http_core (changed)</a></h3> <ul> - <li>REMOVED <code>ap_default_type</code>, <code>ap_requires</code>, all + <li>REMOVED <code>ap_default_type</code>, <code>ap_requires</code>, all 2.2 authnz API</li> <li>Introduces Optional Functions for logio and authnz</li> <li>New function <code>ap_get_server_name_for_url</code> to support IPv6 @@ -161,11 +161,11 @@ <li>Support for mod_request kept_body</li> <li>Support buffering filter data for async requests</li> <li>New <code>CONN_STATE</code> values</li> - <li>Function changes: <code>ap_escape_html</code> updated; + <li>Function changes: <code>ap_escape_html</code> updated; <code>ap_unescape_all</code>, <code>ap_escape_path_segment_buffer</code></li> <li>Modules that load other modules later than the <code>EXEC_ON_READ</code> config reading stage need to call <code>ap_reserve_module_slots()</code> or - <code>ap_reserve_module_slots_directive()</code> in their + <code>ap_reserve_module_slots_directive()</code> in their <code>pre_config hook</code>.</li> <li>The useragent IP address per request can now be tracked independently of the client IP address of the connection, for @@ -193,16 +193,16 @@ <li>New auth_internal API and auth_provider API</li> <li>New <code>EOR</code> bucket type</li> <li>New function <code>ap_process_async_request</code></li> - <li>New flags <code>AP_AUTH_INTERNAL_PER_CONF</code> and + <li>New flags <code>AP_AUTH_INTERNAL_PER_CONF</code> and <code>AP_AUTH_INTERNAL_PER_URI</code></li> - <li>New <code>access_checker_ex</code> hook to apply additional access control + <li>New <code>access_checker_ex</code> hook to apply additional access control and/or bypass authentication.</li> - <li>New functions <code>ap_hook_check_access_ex</code>, - <code>ap_hook_check_access</code>, <code>ap_hook_check_authn</code>, - <code>ap_hook_check_authz</code> which accept + <li>New functions <code>ap_hook_check_access_ex</code>, + <code>ap_hook_check_access</code>, <code>ap_hook_check_authn</code>, + <code>ap_hook_check_authz</code> which accept <code>AP_AUTH_INTERNAL_PER_*</code> flags</li> - <li>DEPRECATED direct use of <code>ap_hook_access_checker</code>, - <code>access_checker_ex</code>, <code>ap_hook_check_user_id</code>, + <li>DEPRECATED direct use of <code>ap_hook_access_checker</code>, + <code>access_checker_ex</code>, <code>ap_hook_check_user_id</code>, <code>ap_hook_auth_checker</code></li> </ul> <p>When possible, registering all access control hooks (including @@ -215,7 +215,7 @@ <p>If your module requires the old behavior and must perform access control checks on every sub-request with a different URI from the initial request, even if that URI matches the same set of access - control configuration directives, then use + control configuration directives, then use <code>AP_AUTH_INTERNAL_PER_URI</code>.</p> @@ -226,7 +226,7 @@ <h3><a name="mod_cache" id="mod_cache">mod_cache (changed)</a></h3> - <p>Introduces a <code>commit_entity()</code> function to the cache provider + <p>Introduces a <code>commit_entity()</code> function to the cache provider interface, allowing atomic writes to cache. Add a <code>cache_status()</code> hook to report the cache decision. All private structures and functions were removed.</p> @@ -267,10 +267,10 @@ <code>set_scoreboard</code> (locking uses the new ap_mutex API)</li> <li>NEW API to drop privileges (delegates this platform-dependent function to modules)</li> - <li>NEW Hooks: <code>mpm_query</code>, <code>timed_callback</code>, and + <li>NEW Hooks: <code>mpm_query</code>, <code>timed_callback</code>, and <code>get_name</code></li> <li>CHANGED interfaces: <code>monitor</code> hook, - <code>ap_reclaim_child_processes</code>, + <code>ap_reclaim_child_processes</code>, <code>ap_relieve_child_processes</code></li> </ul> @@ -363,7 +363,7 @@ <p><code>ap_log_*error</code> are now implemented as macros. This means that it is no longer possible to use <code>#ifdef</code> inside the argument list of <code>ap_log_*error</code>, as this would cause - undefined behavor according to C99.</p> + undefined behavior according to C99.</p> <p>A <code>server_rec</code> pointer must be passed to <code>ap_log_error()</code> when called after startup. This @@ -499,9 +499,9 @@ <dd>This has been renamed to ap_unixd_setup_child(), but most callers should call the added ap_run_drop_privileges() hook.</dd> - <dt><code>conn_rec->remote_ip</code> and + <dt><code>conn_rec->remote_ip</code> and <code>conn_rec->remote_addr</code></dt> - <dd>These fields have been renamed in order to distinguish between + <dd>These fields have been renamed in order to distinguish between the client IP address of the connection and the useragent IP address of the request (potentially overridden by a load balancer or proxy). References to either of these fields must be updated with one of the @@ -515,7 +515,7 @@ <li>When you require the IP address of the client that is connected directly to the server, which might be the useragent or might be the load balancer or proxy itself, use - <code>conn_rec->client_ip</code> and + <code>conn_rec->client_ip</code> and <code>conn_rec->client_addr</code>.</li> </ul> </dd> @@ -574,7 +574,7 @@ </div></div> <div class="bottomlang"> <p><span>Available Languages: </span><a href="../en/developer/new_api_2_4.html" title="English"> en </a></p> -</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div> <script type="text/javascript"><!--//--><![CDATA[//><!-- var comments_shortname = 'httpd'; var comments_identifier = 'http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html'; @@ -592,7 +592,7 @@ var comments_identifier = 'http://httpd.apache.org/docs/2.4/developer/new_api_2_ } })(window, document); //--><!]]></script></div><div id="footer"> -<p class="apache">Copyright 2019 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="apache">Copyright 2024 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- if (typeof(prettyPrint) !== 'undefined') { prettyPrint(); |