William A. Rowe, Jr. wrote:
Give that some thought :)
One thing I'm pondering is a 2.3.0 alpha in the near future.
If only to give the we stay back at version n.x-1 crowd something
to chew on.
Not to mention that it would be good for folks to start exploring
what needs to be fixed in the API
Paul Querna wrote:
I'm not sure what we are supposed to think about?
Lots of people still use 1.3 for their own reasons, its not going to
hold me back on things I would like to do in 2.4 or 3.0.
Good point; maybe this is part of the issue, what we *already* do today
in 2.2 etc, vs. what
Eric Covener wrote:
While the API might be a little ambiguous, and the caller can
explicitly set the timeout, is this a discrepancy APR should
eliminate?
I'm going to add the apr_file_pipe_timeout_set(foo, 0) call instead to
mod_ext_filter unless there are any objections.
+1
Joe Orton wrote:
On Mon, Oct 01, 2007 at 02:22:11AM -0500, William Rowe wrote:
server/Makefile.in;
export_files:
tmp=export_files_unsorted.txt; \
rm -f $$tmp touch $$tmp; \
for dir in $(EXPORT_DIRS); do \
ls $$dir/*.h $$tmp; \
done; \
Jim Jagielski wrote:
On Oct 1, 2007, at 4:07 PM, William A. Rowe, Jr. wrote:
Jim Jagielski wrote:
But, as I read it, the '*' in OPTIONS * does not really
mean a Location *... in other words, it's not a URI per se.
OPTIONS * asks for the capabilities of the server itself,
independent
Jim Jagielski wrote:
Comments?:
Just one;
Index: modules/http/http_core.c
===
--- modules/http/http_core.c(revision 581205)
+++ modules/http/http_core.c(working copy)
@@ -234,6 +234,24 @@
return OK;
}
+static
Paul Querna wrote:
Starting in January 2008, only critical security issues will be fixed in
Apache HTTP Server versions 1.3.x or 2.0.x.
Actually that statement is too narrow; What if we publish a manifesto such
as this?
Apache httpd 1.3 to be retired at it's 10th anniversary
The Apache
Roy T. Fielding wrote:
I was only talking about the OPTIONS /path case. * is a special
case of a true null request -- it should only deal with server
capabilities and ignore Location/Directory configs.
Could you clarify, though? If PROPGET or PUT is supported on some
subset of the server
[EMAIL PROTECTED] wrote:
Log:
Reduce the last change to a minimum, since OPTIONS * does not
include an Allow header field (* is not a resource).
Ignore my previous question; obviously this makes it a non-issue.
[EMAIL PROTECTED] wrote:
Oh, last commit was supposed to say we need to return
DONE so we don't invoke any handlers.
Just so everyone here knows;
svn propset --revprop -r581388 svn:log Return DONE instead of OK to prevent any
further hooks from touching the non-URI OPTIONS * request
and it
I would appreciate the active confirmation of this new parser by at
least a second set of eyeballs. We all know how notorious parsers
are at creating holes in the security of fresh software and code.
The relevant RFC is;
http://www.packetizer.com/rfc/rfc2428
(rfc.net appeared to be offline,
William A. Rowe, Jr. wrote:
I would appreciate the active confirmation of this new parser by at
least a second set of eyeballs. We all know how notorious parsers
are at creating holes in the security of fresh software and code.
The relevant RFC is;
http://www.ietf.org/rfc/rfc2428.txt
Roy T. Fielding wrote:
I don't see why we care, either way.
Could you clarify what we aren't caring about, since your answer was
a bit ambiguous? (Abandon or not, message our users or not, etc)
AIUI this is the desired default behavior from apr; why change httpd
at all? I was receptive to your suggestion/patch to resolve this as
the default on apr 0.9/1.2/1.x branches, per the unix implementation.
Bill
[EMAIL PROTECTED] wrote:
Author: covener
Date: Wed Oct 3 10:17:24 2007
New
--- httpd/httpd/trunk/include/http_protocol.h (original)
+++ httpd/httpd/trunk/include/http_protocol.h Sun Oct 7 06:41:50 2007
@@ -664,6 +664,12 @@
* @param sub_r Subrequest that is now compete
*/
AP_DECLARE(void) ap_finalize_sub_req_protocol(request_rec *sub_r);
+
+/**
+ * Send an
Jeff Trawick wrote:
On 10/8/07, Jim Jagielski [EMAIL PROTECTED] wrote:
Thoughts on adding mod_substitute to 2.2.x under experimental?
if in 2.2.x at all, why not in the normal modules directory? is it
really experimental, or is experimental considered a political
compromise, or is there
Jim Jagielski wrote:
On Oct 9, 2007, at 5:33 AM, Ruediger Pluem wrote:
+const char *allowed = ~$-_.+!*'(),;:@=/; /* allowed+reserved
from
+ ap_proxy_canonenc */
Otherwise looks good.
Would almost make sense to have this as an API
Jim Jagielski wrote:
I might be confused here, but if the response is forced 1.0,
then there are no keepalives in which case we want to *force*
keepalives off.
Actually two different settings, no? 1.0 supported explicit keepalives.
Jim Jagielski wrote:
On Oct 9, 2007, at 12:40 PM, William A. Rowe, Jr. wrote:
Jim Jagielski wrote:
I might be confused here, but if the response is forced 1.0,
then there are no keepalives in which case we want to *force*
keepalives off.
Actually two different settings, no? 1.0
[EMAIL PROTECTED] wrote:
Permit third numerical form of IPv6 addresses, e.g. ::n.n.n.n
although this form will almost certainly fail proxyport equality tests.
With this patch, we now implement RFC2428, which was my only hesitation
to at least throwing out an alpha release for users to
Eric Covener wrote:
I'd like to backport to 2.0.x but it seems like there was a little bit
of caution in the 2.2.x/trunk commits.
Propose it in STATUS and let's see where that goes.
Joe Orton wrote:
3) we can restore the pre-2.2.4 behaviour on Win32 by doing something
simple like the below, without having to mess with the APR procattr code
or continue adding complexity to the log.c code?
-1 not acceptable, you are looping back to dangling pipes, lingering
processes,
Mladen Turk wrote:
William A. Rowe, Jr. wrote:
I had refactored your patch on trunk so that we no longer name the
silly function wait_for_many_objects (since it obviously didn't do
that properly, at least not with any consideration of fairness or
parallel signals). Roy's concerns should
Eric Covener wrote:
Will the transition to a new MS compiler necessarily be on a major
release boundary? Or is this really on the table at any given time
based on the binaries being more or less a convenience?
wrt third-party modules, it seems like we will have to eventually pull
the trigger
Ashwani Kumar Sharma wrote:
I want to make my apache web server listen on IPv6 address. What
settings I need to do. Somebody, please guide.
I have installed the IPv6 on Windows XP. I have installed the apache 2.2.4.
When I am sending the request from the browser, my apache web server is
Paul Querna wrote:
+1 to 192 or 256.
~1, actually I'd be +1 to a patch that lets you configure this anywheres
between nothing and 8192.
However, it would end up being one of those goofy 'nonvolatile' config
settings that can't be tweaked in a graceful restart (just like MaxServers
etc), so we
Niklas Edmundsson wrote:
Could we start by increasing the existing one, which is rather easily
done, and then move on to doing it the fancy way? If someone has a
fancy-patch right now I'm all for that, but pending that I'd prefer
landing some sort of improvement...
I don't quite see the
Jim Jagielski wrote:
Say you are looking for 'foo' and have a bucket that
contains 'jimfoojag'. The fast way to handle this would
be to split off 3 buckets from this, one containing
'jim', the other containing 'jag' and the middle one that
contains the substitute for 'foo' (say it's 'bar'). The
Nick Kew wrote:
Günther Gsenger [EMAIL PROTECTED] wrote:
André Malo:
This spreads another uri escaper copy around. Why can't we take
ap_escape_uri? Without deep digging: what's the difference?
Also I don't like the ' ' = '+' transition, which should not be
applied
forpaths. It's safer to
Marc Mongenet wrote:
Hello,
I compiled httpd-2.2.6-win32-src-r2.zip with Visual C++ 2005 Express
following the instructions given by
http://httpd.apache.org/docs/2.2/platform/win_compiling.html.
On IRC, niq suggested me to post comments/suggestions for improvement
of
Folks, I brought this up on list and don't remember a response.
I'm wondering if we need to do this handshake before using one
of mod_proxy's SSL client streams. I believe we do in the case
of connecting to ftps:// if we ever support it, due to the fact
that we will attempt to read off the
Plüm wrote:
Sorry, but I do not get the purpose of this patch.
Why reading from our *client* (regardless if it is SSL or not)
when the backend is SSL?
The original flaw, maybe long gone, is that mod_ssl implementation was
pull; on first read handshake would occur. The INIT blocking-flag was
Ruediger Pluem wrote:
As far as I remember there was a desire to release 2.2.7 soon as 2.2.6
introduced some incompatibilities with mod_fastcgi and mod_perl on Windows due
to changes to avoid file descriptor leaks on Windows. Other Bill worked hard
on the needed fixes in APR and so the original
Mads Toftum wrote:
On Sun, Oct 28, 2007 at 04:17:50PM +0200, Graham Leggett wrote:
I am not so sure. mod_proxy already supports client behaviour, and has the
bonus of using bucket brigades natively allowing zero copy natively.
That'd be true for serf as well, right? The whole point of
FYI - mod_echo illustrated that there's value in recording info by connection
into the scoreboard, as opposed to only by request.
We could just as easily move scoreboard-update-by-conn into scoreboard.c - which
would we rather do?
Bill
[EMAIL PROTECTED] wrote:
Author: bnicholes
Date: Tue Oct
Issac Goldstand wrote:
The same patchset can be used for 2.2.x branch pretty much as is with
the single addition of backporting the apr_socket_sendto function from
trunk (it's broken in the APR that ships with 2.2.x)
We agree that's true - have you looked at apr 1.2.x branch lately? A week
Issac Goldstand wrote:
Nice. A cursory look appears to match what I have.
I also dug up another nugget - a complete patch against httpd-2.2.6 for
the UDP support (excluding only the APR recvfrom issue) - I thought I
had it lying around somewhere. I included two; one with and one without
the
[EMAIL PROTECTED] wrote:
Author: rpluem
Date: Sun Nov 4 03:20:11 2007
New Revision: 591760
URL: http://svn.apache.org/viewvc?rev=591760view=rev
Log:
* Use the same declaration for ap_time_process_request as in the header file.
PR: 43789
Submitted by: Tom Donovan Tom.Donovan acm.org
Reviewed
Closed the bug so nobody else goes to 'fix' this ;-)
Jim Jagielski wrote:
Thanks... changed on people so it'll update at the next rsync
On Nov 7, 2007, at 9:31 AM, Guenter Knauf wrote:
Hi,
the file / link:
http://www.apache.org/dist/httpd/CURRENT-IS-2.2.4
seems no longer correct.
Guen.
/ignore - sorry for the noise.
Original Message
Subject: Re: HTML request accesses my router
Date: Thu, 08 Nov 2007 19:17:59 -0500
From: Eric Maurier [EMAIL PROTECTED]
Organization: Ross-Tech.com
To: Apache Security Response Team [EMAIL PROTECTED]
CC: Uwe Ross [EMAIL PROTECTED]
Eric,
once a year, forwarding notices from [EMAIL PROTECTED] to [EMAIL PROTECTED]
I completely screw up and let autocomplete pick up dev@ - I'm sorry this just
occurred and want to be certain you are aware ASAP!
Fortunately it does seem to be a local access junction, most router hardware
will
Ruediger Pluem wrote:
On 11/13/2007 04:39 PM, Justin Erenkrantz wrote:
I find that mod_proxy is incredibly complex and doesn't even do the
things that it claims to do properly. Rather than spend an inordinate
amount of time trying to fix it, I think we'd be better off trying to
go in a
Justin Erenkrantz wrote:
On Nov 14, 2007 9:06 AM, Issac Goldstand [EMAIL PROTECTED] wrote:
[ ] Immediate adoption as an included module (pending IP clearance via
the incubator)
[X] Immediate adoption as a subproject (pending IP clearance via the
incubator)
- But, no separate mailing lists and
Ruediger Pluem wrote:
Now that the TR of APR / APR-UTIL is in progress (Thanks Other Bill)
httpd 2.2.7 seems to come in sight. There are about 10 backport
proposals in the STATUS file that are only missing one vote. So
come on it is voting and review time guys :-)).
There is one backport
-rv = apr_file_pipe_create(((*pod)-pod_in), ((*pod)-pod_out), p);
+rv = apr_file_pipe_create_ex(((*pod)-pod_in), ((*pod)-pod_out),
+ APR_WRITE_BLOCK, p);
if (rv != APR_SUCCESS) {
return rv;
}
Hrm.
Reviewing this patch, we break prefork
Sriram Ganesan wrote:
there are some checks which
are different compared to the normal GCC compiler. The difference being
that:
checking for memmove... no
checking for bcopy... no
checking for strncasecmp... no
checking for strcasecmp... no
checking for strdup... no
checking for strstr... no
Justin Erenkrantz wrote:
Once we switched our code to supporting external PCREs, in my opinion,
we should have just dropped the whole vendor branch concept as it
serves no legitimate purpose any more. If the PCRE guys are doing
releases now (it seems someone is home now), then we should just
Worse than a leak; conf-pool should be const, touching it explodes the
copy-on-write semantics of the conf pool memory (which otherwise is a
single common resource). There are better pools to abuse, if unavoidable,
such as process pool.
Jeff Trawick wrote:
looks like a leak to me; what do you
kaby wrote:
For the primarily web application is no longer static.
Considering factors like cache, instruction prediction, I suppose randomized
request is need to avoid possible bias in benchmark.
So I wanna proposal a patch for this. Any suggestion?
ab.c isn't the place for such work, and you
Jim especially,
Attached is what I believe are checks that were only relevant to
the existence of the glob() functionality. Now that we are doing
an apr_fnmatch, they seem obsolete and should just be chucked
(although the patch simply marks them out for verification.
Could you please review if
There seems to be several consistent bugs/misassumption throughout the
lookup values of ftp_limitlogin.c's logic. As background; there is
actually only one LimitDB file for the entire running server instance.
* the dkey's aren't keyed by virtual host, rendering the net
results server-wide
URL: http://svn.apache.org/viewvc?rev=601843view=rev
Log:
Come closer to a release by backing-up the version from Covalent-numbering
series to an ASF numbering series, and prepare for the first GA release
to be numbered 1.0.0.
This means 0.9.0 is an obvious numbering schema for alpha/beta's.
Jim Jagielski wrote:
I'll take an effort in addressing them... I think the
issues are due to the fact that the actual updates to
the doccos lagged behind changes to the codebase...
Are you certain? Do we mean to test 'wrowe' on poweruser.example.com
is the same person as 'wrowe' on
Guenter Knauf wrote:
Just a hint: last time I tested also with cURL which caused for whatever reason
a segfault with mod_ftp (r525888); so if possible you should also try some
transfers with cURL...
Hmmm - any chance you were using IPv6? The patches I committed
today resulted from chasing
Guenter Knauf wrote:
Hi,
Who's interested in seeing a TR and helping make the release happen?
me.
Cool. I've backed out the extra ABOR aliasing from trunk so we can tag
a beta, and if someone cares they can add compensation for all of the
weirder OOB behaviors that we see in the 'real
Guenter Knauf wrote:
Hi,
here's what makes it compile - however first hunk seems not nice...
just commited slightly modified patch.
Much prettier, thanks :)
Ruediger Pluem wrote:
Thanks folks for all the reviewing work done. From my perspective there
is now nothing left between us and 2.2.7.
FYI you failed to backport the win32 build file to mod_substitute,
so I'll go ahead and do that along with review the entire package
today so it's ready as a
Ruediger Pluem wrote:
On 12/09/2007 10:02 PM, Guenter Knauf wrote:
Hi,
question regarding mod_substitute docu:
This is an experimental module and should be used with care.
should this warning remain now that its moved out of experimental?
+1 to remove experimental from the docs.
+1 from
[EMAIL PROTECTED] wrote:
Author: rpluem
Date: Sat Dec 8 08:50:12 2007
New Revision: 602503
@@ -28,16 +28,16 @@
#include http_protocol.h /* For index_of_response(). Grump. */
#include http_request.h
-/* Generate the human-readable hex representation of an unsigned long
- * (basically a
Michael Clark wrote:
apr_os_dir_put doesn't create a working apr_dir_t i.e. apr_dir_read will
not work on the created apr_dir_t
Favor - please don't post to multiple lists, have a bit of patience;
feedback was posted to [EMAIL PROTECTED]
Michael Clark wrote:
Hi Folks,
I posted a note about my privilege separation patches the other day
and received some good private help/feedback, and have now made the
patches a considerable amount more portable and they are using apr
much more extensively.
Cool stuff! I'll start reviewing
William A. Rowe, Jr. wrote:
Michael Clark wrote:
apr_os_dir_put doesn't create a working apr_dir_t i.e. apr_dir_read
will not work on the created apr_dir_t
Favor - please don't post to multiple lists, have a bit of patience;
feedback was posted to [EMAIL PROTECTED]
Ok - confused Iain Wade's
Mladen Turk wrote:
Jir wrote:
is there any reason why HTTP_INTERNAL_SERVER_ERROR returned by proxy
handler cannot failover to another worker?
Because HTTP_INTERNAL_SERVER_ERROR is used to represent either
misconfiguration or even worse things like memory allocation
failures. In essence non
Jim Jagielski wrote:
Anyone opposed to us shooting for a TR early next week?
If we can get a couple of security-related-but-not-really patches
committed to 2.0 I'd like to see that as well. I'm offering, but
if you would enjoy it, I'll just focus on win32 src/binary packages
all around.
Bill
Oden Eriksson wrote:
Den Friday 14 December 2007 20.24.35 skrev Jim Jagielski:
From what I can see, both 1.3 and 2.2 are backport
free, so it's just 2.0 right now.
Yup - and the review of significant 2.0 patches would only take
an hour or two, it's not that complex - things that were
William A. Rowe, Jr. wrote:
There's a simple way of not-so-rudely saying ...
Sorry if this came across harshly Odin, I watch those dialogs
daily on php-dev, I'd hate to see httpd-dev polluted with the
same volume of self interest and vitriol. Let me make sure
I answered what you might have
For Netware, where ./configure.apxs doesn't work...
[EMAIL PROTECTED] wrote:
Author: wrowe
Date: Fri Dec 14 20:36:18 2007
New Revision: 604390
URL: http://svn.apache.org/viewvc?rev=604390view=rev
Log:
In-tree builds were broken because loggers aren't in the
includes path, and mod_log_config.h
mod_ftp fans;
At last, I came up with a trivial strategy for doing autoconf-like
tests, using nothing except apxs httpd/build/ elements, so mod_ftp
is really ready for feedback across any platform.
Please fetch up the newly prepared httpd-mod_ftp-0.9.0.tar.[gz|bz2]
(and its md5/asc sigs) from:
Sorry folks, disappointing news, but 0.9.0 doesn't pass muster.
If you want to help verify that 0.9.1 is more likely to be ready
for release, please, apply the attached patch to 0.9.0 before you
attempt to ./configure; make install.
If my message is too late,
chmod 755 `apxs -q
Jim, this was part of your initial import. I don't know that these
really have a practical application, but would you review these and
determine if the utils/ tree should stay or be rm'ed before 1.9.1
is tagged?
For tests/perl-framework/, I don't know that it makes sense to
distribute this with
As I wrote the templates of mod_ftp's out-of-tree schema, I was
thinking of an approach that would work for mod_mbox/smtpd/mod3/arm4
or even mod_dns.
This approache is ready for review; I'm wondering if we might want to
create a 'template' for a mod_example style build? This might make it
William A. Rowe, Jr. wrote:
I'm thinking that httpd/mod_ftp/trunk/tests/perl-framework might move
over to httpd/test/trunk/mod_ftp-perl-framework for now. After it
has a few more eyeballs, that could just be merged into the actual
.../perl-framework tree (as long as it stays out of the way
William A. Rowe, Jr. wrote:
I suggest
httpd/test/
httpd/
(all testing modules related to httpd core)
test/[trunk|tags|branches]
(renaming perl-framework, which is too wordy anyways)
Rethought this; framework makes sense (the fact that it's written
in perl is beside the point
Joe Orton wrote:
On Sun, Dec 16, 2007 at 08:37:08PM +0100, Stefan Fritsch wrote:
*) http_protocol: Escape request method in 413 error reporting.
Determined to be not generally exploitable, but a flaw in any case.
PR 44014 [Victor Stinner victor.stinner inl.fr]
This is CVE-2007-6203.
Guenter Knauf wrote:
the files from the tarball compile cleanly for NetWare without any change for
both 2.0.x and 2.2.x;
nothing more yet tested for the moment...
That's in-tree, then, or using ./configure.apxs? The reason this couldn't
work out-of-tree without defining FTP_APXS_BUILD is
Stefan Fritsch wrote:
I agree. It might be exploitable with buggy browser plugins using HTTP
request splitting. See e.g.
http://www.adobe.com/support/security/advisories/apsa06-01.html
Request splitting was previously addressed in httpd.
Guenter,
see the logic in (top level) Makefile.apxs which invokes the
build/addloadexample.awk script (I recall you can rely on an awk
being present.)
Rather than loading the module inside extra/ftpd.conf, I coupled
it in 'in the style of' the other extra/*.conf sections, and the new
awk
William A. Rowe, Jr. wrote:
Guenter,
see the logic in (top level) Makefile.apxs which invokes the
build/addloadexample.awk script (I recall you can rely on an awk
being present.)
Oh - we need to add a -v DSO=.nlm - I've already adjusted Makefile.apxs
accordingly.
Remaining noise after these two are applied to trunk are listed below.
It's looking awfully sloppy - and prone to optimization bugs.
URL: http://svn.apache.org/viewvc?rev=605073view=rev
Log:
Two type mismatch fixes previously committed to trunk\
and forgotten from backports
@@ -37,7 +37,8 @@
Guenter Knauf wrote:
Hi Bill,
Any concerns with my new approach?
no real concerns - but personally I would prefer to have the load statements
inside each conf file;
also because for now we anyway distribute it separately, and once we have it
inside httpd then anyway things might go other
William A. Rowe, Jr. wrote:
Remaining noise after these two are applied to trunk are listed below.
It's looking awfully sloppy - and prone to optimization bugs.
URL: http://svn.apache.org/viewvc?rev=605073view=rev
Log:
Two type mismatch fixes previously committed to trunk\
and forgotten from
So here's the suggested transition to restore some sanity to the
test subproject. Feedback, please?
svn mkdir https://svn.apache.org/repos/asf/httpd/test/flood
svn mkdir https://svn.apache.org/repos/asf/httpd/test/flood/branches
svn mkdir https://svn.apache.org/repos/asf/httpd/test/flood/tags
William A. Rowe, Jr. wrote:
So here's the suggested transition to restore some sanity to the
test subproject. Feedback, please?
one exception; this tag didn't nest perl-framework in the tag, so it's
simply;
svn cp https://svn.apache.org/repos/asf/httpd/test/tags/APACHE_TEST_1_20/
https
William A. Rowe, Jr. wrote:
mod_ftp fans;
At last, I came up with a trivial strategy for doing autoconf-like
tests, using nothing except apxs httpd/build/ elements, so mod_ftp
is really ready for feedback across any platform.
Please fetch up the newly prepared httpd-mod_ftp-0.9.0.tar.[gz|bz2
Niklas Edmundsson wrote:
You might want to have a go at the configure.apxs before doing that. It
seems to contain some bashisms that shows up on debian/ubuntu machines
which uses dash as /bin/sh:
% ./configure.apxs
test: 8: ==: unexpected operator
test: 19: ==: unexpected operator
Takashi Sato wrote:
mod_ftp.c:831: warning: no previous prototype for 'ftp_epsv_ignore_family'
No headers declare ftp_epsv_ignore_family, it is without AP_DECLARE and no
sources except mod_ftp.c call or use it.
It is not clear where it is a function intended to be called from.
3) only
Guy Ferraiolo wrote:
I'm ready to do this tomorrow and I have asked this question before but
so long ago I dont' recall. I have a patch which is in the standard
format. Do I include it as text in an email or attached?
diff -u (-U3) is the preferred format; attachments are less likely to
be
Victor Wagner wrote:
On 2007.12.19 at 10:10:54 +0100, Yann wrote:
The changes regarding X509V3_EXT_print() seems more problematic since the
extensions values are used in string
comparison (strcmp and likes), hence the human readable version, and the
I hope that saying human readable you
Nick Kew wrote:
William A. Rowe, Jr. wrote:
Talking of windows builds, where's mod_ssl seems to be something of
a FAQ in user support. Why is it a problem *now* to include it?
You can find some of that discussion burried in legal-discuss@, while
the new VP of legal affairs is taking up
Graham Leggett wrote:
William A. Rowe, Jr. said:
The problem is that packaging is almost a 20/20 hindsite game. There's
no way we should expect that all of these many platform specifics can
all be maintained pre-release. That's why, in the Win32 .msi case,
there is a seperate httpd/httpd
Randy Kobes wrote:
On Tue, 11 Oct 2005, William A. Rowe, Jr. wrote:
Question;
I'm looking for input what version of visual c++ we should build apr 1.x
and httpd 2.1.x and onwards with. As most are aware, discrepancies in
the clib mean that mismatched posix open()/close(), malloc()/free() can
Glenn Strauss wrote:
On Mon, Oct 10, 2005 at 10:54:36AM -0400, Jim Jagielski wrote:
I will be TR'ing 1.3.34 On Tues or Weds
May I humbly request inclusion of a patch I wrote almost a year ago?
http://issues.apache.org/bugzilla/show_bug.cgi?id=31858
|31858|New|Maj|2004-10-22|regular
Nick Kew wrote:
Given 2.1's current beta status, what rules govern breaking the ABI
right now?
Break it. 2.odd has no ABI/API rules. 2.even is constrained, so since
we will be stuck with the ABI for a year or two, while 2.2 is supported,
better to be stuck with the best API we could come up
Thank you everyone for testing, especially the infrateam for picking
this up on Ajax and really stressing it under mod_mbox (in spite of
a few more fixes required to mbox's mime processing :)
Although the site is updated, starting the clock on the announce till
early tomorrow aftn (america time)
Sander Temme wrote:
On Oct 13, 2005, at 5:34 PM, Jim Jagielski wrote:
Look for the Apache HTTP Server 1.3.34 prerelease tarballs in:
http://httpd.apache.org/dev/dist/
Please test :)
It's a little after the fact, but I ran the regex tests on the two
Solaris boxes in my garage that
Roy T.Fielding wrote:
It has been featured in multiple PRs since then for both GNATS (4490)
and Bugzilla (PR 15242). Are there any objections to removing it now,
both here and in mod_cgid? It is currently preventing folks from
implementing new services (WEBDAV and Atom, among others) via CGI.
Francis ANDRE wrote:
Hi
I was not able to found the MSVC 7.1 solution for building the httpd
server but only the MSVC 6.0. Is it missing or something else??
Simply load Apache.dsw in MSVC 7.1 - which will migrate all the .dsp files
to .vcproj's and creates Apache.sln.
Joshua, I appologize for pre-staging - was hoping this would save some
cycles in this extremely busy week and didn't mean to get in the way of
other devs updating the site.
Jim, I'm happy to push the website up to date when you stage the files
for release. [FYI - I'll create the Win32 installer
Forgot to ask here, too, for good measure :)
Original Message
Subject: Win32 1.3.34 binary installs available
Date: Tue, 18 Oct 2005 13:56:57 -0500
From: William A. Rowe, Jr. [EMAIL PROTECTED]
Reply-To: testers@httpd.apache.org
To: testers@httpd.apache.org
If anyone has a few
Ruediger Pluem wrote:
Meanwhile I identified 3 others positions in the proxy code path which can
cause this kind of trouble.
Please find the updated patches attached. Using APR_BRIGADE_CONCAT in a loop
with ap_get_brigade
on the same brigade seems to be troublesome :-).
Ruediger - I'm
601 - 700 of 6128 matches
Mail list logo
