time with your delimiter which it then remembers and on each subsequent
call it returns the next token. Obviously if multiple threads are
calling it you will have a problem. Most systems have a reentrant version
- of of the function called <code>strtok_r()</code> where you pass in an
+ of the function called <code>strtok_r()</code> where you pass in an
extra argument which contains an allocated <code>char *</code> which the
function will use instead of its own static storage for maintaining
the tokenizing state. If you are using <a href="http://apr.apache.org/"
be done offline so the web server machine is not burdened
by processing the log files. Most log analysis packages
understand the Common Log Format. The fields in the log
- lines are explained in in the following:
+ lines are explained in the following:
</p>
<usage>
<p>The <directive module="mod_auth_form">AuthFormMethod</directive> directive specifies
the name of an HTML field which, if present, will contain the
- mimetype of the request to to submit should login be successful.</p>
+ mimetype of the request to submit should login be successful.</p>
<p>By populating the form with fields described by
<directive module="mod_auth_form">AuthFormMethod</directive>,
like <code>JSESSIONID</code> or <code>PHPSESSIONID</code>,
and it depends on the backend application server that support sessions.
If the backend application server uses different name for cookies
- and url encoded id (like servlet containers) use | to to separate them.
+ and url encoded id (like servlet containers) use | to separate them.
The first part is for the cookie the second for the path.<br />
Available in Apache HTTP Server 2.4.4 and later.
</td></tr>
<dd>The path component of the requested URI,
such as "/index.html". This notably excludes the
- query string which is available as as its own variable
+ query string which is available as its own variable
named <code>QUERY_STRING</code>.</dd>
<dt><code>THE_REQUEST</code></dt>
<usage>
<p>The <directive>CTSCTStorage</directive> directive sets the name of a
- directory where SCTs and SCT lists will will be stored. If <em>directory</em>
+ directory where SCTs and SCT lists will be stored. If <em>directory</em>
is not absolute then it is assumed to be relative to <directive module="core">
DefaultRuntimeDir</directive>.</p>
AP_FN_ATTR_NONNULL_ALL;
/**
- * Test if the given path has an an absolute path.
+ * Test if the given path has an absolute path.
* @param p The pool to allocate from
* @param dir The directory name
* @note The converse is not necessarily true, some OS's (Win32/OS2/Netware) have
* the buckets in bbinp and read the data from buckets and invoke
* sed_eval_buffer on the data. libsed will generate its output using
* sed_write_output which will add data in ctx->bb. Do it until it have
- * atleast one bucket bucket in ctx->bb. At the end of data eos bucket
+ * atleast one bucket in ctx->bb. At the end of data eos bucket
* should be there.
*
* Once eos bucket is seen, then invoke sed_finalize_eval to clear the
}
}
- /* The names may be identical in respects other other than
+ /* The names may be identical in respects other than
* filename case when strnatcmp is used above, so fall back
* to strcmp on conflicts so that fn1.01.zzz and fn1.1.zzz
* are also sorted in a deterministic order.
}
if (buffer->length > inl) {
- /* we have have enough to fill the caller's buffer */
+ /* we have enough to fill the caller's buffer */
memmove(in, buffer->value, inl);
buffer->value += inl;
buffer->length -= inl;
/* Some HTTP/1.0 clients are known to choke when they get
* a 300 (multiple choices) response without a Location
- * header. However the 300 code response we are are about
+ * header. However the 300 code response we are about
* to generate will only reach 1.0 clients which support
* transparent negotiation, and they should be OK. The
* response should never reach older 1.0 clients, even if
module AP_MODULE_DECLARE_DATA ident_module;
/*
- * Optional function for the core to to the actual ident request
+ * Optional function for the core to the actual ident request
*/
static const char *ap_ident_lookup(request_rec *r)
{
* done. If the value matches the string or regular expression, the
* environment variables listed as var ... are set. Each var can
* be in one of three formats: var, which sets the named variable
- * (the value value "1"); var=value, which sets the variable to
+ * (the value "1"); var=value, which sets the variable to
* the given value; or !var, which unsets the variable is it has
* been previously set.
*
/* WE only understand chunked. Other modules might inject
* (and therefore, decode) other flavors but we don't know
- * that the can and have done so unless they they remove
+ * that the can and have done so unless they remove
* their decoding from the headers_in T-E list.
* XXX: Make this extensible, but in doing so, presume the
* encoding has been done by the extensions' handler, and
}
if (buffer->length > inl) {
- /* we have have enough to fill the caller's buffer */
+ /* we have enough to fill the caller's buffer */
memmove(in, buffer->value, inl);
buffer->value += inl;
buffer->length -= inl;
projects / apache / commitdiff