- Original Message -
From: William A. Rowe, Jr. [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 28, 2001 10:55 PM
Subject: Begging your pardons,
but is anyone familiar with the following failure cases on win32?
modules\access..FAILED tests 4, 20-21, 24, 26, 28,
From: Randy Kobes [EMAIL PROTECTED]
Sent: Sunday, December 30, 2001 12:30 PM
From: William A. Rowe, Jr. [EMAIL PROTECTED]
Sent: Friday, December 28, 2001 10:55 PM
but is anyone familiar with the following failure cases on win32?
modules\access..FAILED tests 4, 20-21, 24, 26, 28,
Adam Sussman wrote:
Mod_proxy truncates the status line returned by the proxied
server. One character gets snipped off of the end of the
status line.
Are you 100% sure the buffer is big enough to do this? If the buffer is
of size len the zero will be written past the end of the buffer.
David Reid [EMAIL PROTECTED] writes:
Try starting the server with another server already running on the same
ports. It'll die saying no listening ports available, right? That's cool.
useful even. What's not is what it says next.
[Fri Dec 28 20:39:26 2001] [alert] no listening sockets
William A. Rowe, Jr. wrote:
Another side issue that I notice; we should _REALLY_ be
presenting MULTIPLE CHOICES rather than serving the smallest
file. The smallest file -hack- is exactly that, someone
worthless for reasons debated on this list many times.
If you are referring to the past
From: Rodent of Unusual Size [EMAIL PROTECTED]
Sent: Sunday, December 30, 2001 10:14 AM
William A. Rowe, Jr. wrote:
Another side issue that I notice; we should _REALLY_ be
presenting MULTIPLE CHOICES rather than serving the smallest
file. The smallest file -hack- is exactly that,
There are still issues with PATH_INFO/QUERY_STRING on redirected
(multiviewed) ap_lookup_sub_req_dirent CGI's that I'd like to
tackle. It may be an API change, so the sooner the better.
The lookup file/dirent schema is really cool, except that it
doesn't give us a graceful point to insert the
I believe Daniel brought this up (or at least he pointed it out to me)
that we go way overboard with logging directives;
* Syntax:
*
*TransferLog fn Logs transfers to fn in standard log format, unless
*a custom format is set with LogFormat
*LogFormat
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]]
Isn't it time to drop TransferLog and CookieLog?
+1
We can accomplish the same by allowing that LogFormat provides the default
for the CustomLog directive, in the absense of an optional [format] arg.
I haven't looked in detail, but
Hey, I have two questions here:
1) I'm working on making sure that directives in the Apache 1.3.x
httpd.conf are sync'd to the 2.0 httpd.conf. Can anyone confirm a need
for this? If so, I'll send a patch that does this.
2) Quite a while ago, Martin committed PNG format analogs of the GIFs in
From: Joshua Slive [EMAIL PROTECTED]
Sent: Sunday, December 30, 2001 11:53 AM
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]]
Isn't it time to drop TransferLog and CookieLog?
+1
We can accomplish the same by allowing that LogFormat provides the default
for the CustomLog
According to William A. Rowe, Jr.:
Isn't it time to drop TransferLog and CookieLog?
+1
ciao...
--
Lars Eilebrecht - Just give me the coffee...
[EMAIL PROTECTED] - and no one will get hurt.
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]]
I agree it's simplest, but under my proposal, we lost no functionallity.
If we agree nobody uses the 'default' format TransferLog, then
I'm fine with
your suggestion. But I rather guess this is too radical, and some users
probably
Dale Ghent wrote:
Hey, I have two questions here:
1) I'm working on making sure that directives in the Apache 1.3.x
httpd.conf are sync'd to the 2.0 httpd.conf. Can anyone confirm a need
for this? If so, I'll send a patch that does this.
httpd.conf of 2.0 is not backward compatible with
On Sun, 30 Dec 2001, Eli Marmor wrote:
| Dale Ghent wrote:
|
| Hey, I have two questions here:
|
| 1) I'm working on making sure that directives in the Apache 1.3.x
| httpd.conf are sync'd to the 2.0 httpd.conf. Can anyone confirm a need
| for this? If so, I'll send a patch that does this.
On Sun, 30 Dec 2001, William A. Rowe, Jr. wrote:
Isn't it time to drop TransferLog and CookieLog?
We can accomplish the same by allowing that LogFormat provides the default
for the CustomLog directive, in the absense of an optional [format] arg.
And if we offer a built-in (or
On Sun, 30 Dec 2001, William A. Rowe, Jr. wrote:
And if we offer a built-in (or default-config'ed) 'cookie' format,
of %{Cookie}n \%r\ %t, then it's a two bit change to turn a CookieLog
into a CustomLog file cookie command.
I added the %{COOKIE_NAME}C to 2.0 for logging a simple cookie. This
From: Dale Ghent [mailto:[EMAIL PROTECTED]]
What I'm more-or-less referring to are the Language-related stuff and
IfModule containers (as well as bringing up some of the more informative
comments and such from 1.3.)
Apache 2.0's httpd.conf is based off of 1.3.9's, and there have been a
On Sun, Dec 30, 2001 at 02:58:16PM +0200, Graham Leggett wrote:
Adam Sussman wrote:
Mod_proxy truncates the status line returned by the proxied
server. One character gets snipped off of the end of the
status line.
Are you 100% sure the buffer is big enough to do this? If the buffer
if is there any valid reason to process arguments in mod_include
in series, as we do? An example patch of a more flexible set
tag is attached, for illustration.
It further unsets the variable, if there is no value. Any reason
not to introduce this?
Bill
handle_set.patch
Description:
the follow SSI illustrates the versitility of the new regex features
of mod_include. Throw it in a HEADER.html, turn on the INCLUDES filter,
and play :)
form
Show me a
select name=F
option !--#if expr=$QUERY_STRING = /F=0/ --selected
!--#endif -- value=0 Plain
William A. Rowe, Jr. wrote:
if is there any valid reason to process arguments in mod_include
in series, as we do? An example patch of a more flexible set
tag is attached, for illustration.
It further unsets the variable, if there is no value. Any reason
not to introduce this?
Bill
The
22 matches
Mail list logo