While doing some work on mod_sparql I found that some of the
functionality i had assumed we already had in apr-util was actually
available in apreq. Further examination revealed various parts of the
library code that I feel really belong in apr-util.
I talked briefly with joes and he seemed to be
david reid wrote:
While doing some work on mod_sparql I found that some of the
functionality i had assumed we already had in apr-util was actually
available in apreq. Further examination revealed various parts of the
library code that I feel really belong in apr-util.
I talked briefly with joes
Jonathan Vanasco wrote:
just a heads up:
This was fixed in SVN and will be fixed on the website with 2.08.
--
Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior
On 07/28/2006 03:26 AM, Sander Temme wrote:
All of these hang on the t/protocol/nntp-like.t. I'll try and put a
patch into that test that skips if we're on FreeBSD and accf_http.ko or
accf_data.ko are loaded.
I am neither an expert on FreeBSD nor on accept filters, but wouldn't it be
On 07/27/2006 02:37 PM, Jean-frederic Clere wrote:
Ruediger Pluem wrote:
You want to check all the connections of the pool corresponding to the
worker but not all the workers.
Not all at the same time, but only the one I actually leased.
If it is not that does not mean
necessarily
On Thursday 27 July 2006 18:36, Sander Temme wrote:
Have you reviewed the patch? This is a small modification that takes
unsupported code out of the compile path when building with -DDEBUG.
I'm not happy with applying *any* local patch to a third-party package.
With PCRE we have a quite a
+1 on all, tested on OS X 10.4.7...
Will try on Sol8 and SUSE later on today...
On Jul 27, 2006, at 2:37 PM, William A. Rowe, Jr. wrote:
Chinese firedrill time folks.
There is a vulnerability affecting mod_rewrite which this release
addresses.
See the recent commit activity for detail.
On Jul 26, 2006, at 12:11 PM, Jean-frederic Clere wrote:
Hi,
I have started to write a generic health-checker for mod_proxy. I
would like to change the macro PROXY_WORKER_IS_USABLE() to a
routine in proxy_util.c.
Why? We're simply checking bits... I can't see bothering
with the
yeah, it's a bit of an overhead, but it allows
for one-to-one mapping of SVN commits to each new
feature. And it makes it easier for
people to follow what each smallish patch
does (and therefore +1 it) rather than wrapping
their heads around something larger.
On Jul 26, 2006, at 11:30 AM, Mladen
Apache HTTP Server 2.2.3 Released
The Apache Software Foundation and The Apache HTTP Server Project are
pleased to announce the release of version 2.2.3 of the Apache HTTP Server
(Apache).
This version of Apache is principally a bug and security fix release. The
following
Hi,
I have committed the code to get comments on some points:
- Does it make sense to include from support objects from modules/proxy?
- Does the mod_proxy_health_checker is the right way to go? - I mean: one part
is storing the worker information to use it in an external process and
Hi,
I have committed the code to get comments on some points:
- Does it make sense to include from support objects from modules/proxy?
- Does the mod_proxy_health_checker is the right to do? - I mean: one
part is storing the worker information to use it in an external process
and the other is
On Jul 28, 2006, at 2:31 AM, Nick Kew wrote:
I'm in two minds about that. There is the workaround of
configure --with-pcre
but where does that leave packages? PR#27550 names two
modules that needed to work around the bundled PCRE:
mod_php and mod_caml. That implies two workarounds for the
On Jul 27, 2006, at 1:36 PM, William A. Rowe, Jr. wrote:
Roy T. Fielding wrote:
That line is for the product name, not the project name.
And - I understood that our product is the Apache HTTP Server,
not httpd.
At least that's been the consensus in the docs project for the
last three
Roy T. Fielding wrote:
People discuss what to put in the Announcement text on every release,
but the only discussion I've seen about our product name was Paul's
suggestion we change it to d.
yeah, that was funny :)
--
On 28.07.2006 18:34, [EMAIL PROTECTED] wrote:
Author: jfclere
Date: Fri Jul 28 09:33:58 2006
New Revision: 426604
URL: http://svn.apache.org/viewvc?rev=426604view=rev
Log:
First try to put togother an external health checker for mod_proxy.
Modified:
On Jul 28, 2006, at 12:34 PM, [EMAIL PROTECTED] wrote:
Author: jfclere
Date: Fri Jul 28 09:33:58 2006
New Revision: 426604
URL: http://svn.apache.org/viewvc?rev=426604view=rev
Log:
First try to put togother an external health checker for mod_proxy.
Just coming back from OSCON, I haven't
Roy T. Fielding wrote:
It is the name of the product containing a whole bunch of source code
and many binaries, one of which is sometimes called httpd. The tarballs
are called httpd. The legal notices will be called httpd, and the links
to the artifacts will be called httpd. The only
On Jul 28, 2006, at 1:54 PM, jean-frederic clere wrote:
Hi,
I have committed the code to get comments on some points:
- Does it make sense to include from support objects from modules/
proxy?
- Does the mod_proxy_health_checker is the right way to go? - I
mean: one part is storing the
Em 28/07/2006, às 13:34, [EMAIL PROTECTED] escreveu:
Author: jfclere
Date: Fri Jul 28 09:33:58 2006
New Revision: 426604
...
+
+static const slotmem_storage_method *checkstorage = NULL;
+static ap_slotmem_t *myscore=NULL;
Indentation consistency ? myscore=NULL
+
+if (!port) {
+
Jim Jagielski wrote:
On Jul 28, 2006, at 1:54 PM, jean-frederic clere wrote:
Hi,
I have committed the code to get comments on some points:
- Does it make sense to include from support objects from modules/
proxy?
- Does the mod_proxy_health_checker is the right way to go? - I
mean: one
Jim Jagielski wrote:
On Jul 28, 2006, at 12:34 PM, [EMAIL PROTECTED] wrote:
Author: jfclere
Date: Fri Jul 28 09:33:58 2006
New Revision: 426604
URL: http://svn.apache.org/viewvc?rev=426604view=rev
Log:
First try to put togother an external health checker for mod_proxy.
Just coming back
On Jul 28, 2006, at 4:03 PM, Jean-frederic Clere wrote:
Jim Jagielski wrote:
On Jul 28, 2006, at 1:54 PM, jean-frederic clere wrote:
Hi,
I have committed the code to get comments on some points:
- Does it make sense to include from support objects from
modules/ proxy?
- Does the
Many compile warnings when compiling with maint-mode:
mod_proxy.c: In function 'add_pass':
mod_proxy.c:1176: warning: implicit declaration of function
'proxy_checkstorage_add_entry'
mod_proxy.c: In function 'proxy_post_config':
mod_proxy.c:1870: warning: implicit declaration of function
On Jul 28, 2006, at 12:32 PM, William A. Rowe, Jr. wrote:
From this perspective and for clarity, while we are on the subject,
perhaps
apache-httpd-X would be the appropriate package names, and
seems that
would be consistent with how most many ASF projects are
distributing their
tarballs
On Friday 28 July 2006 19:51, Roy T. Fielding wrote:
Our product is
apache_1.3.37.tar.gz
httpd-2.0.59-win32-src.zip
httpd-2.0.59.tar.gz
httpd-2.2.3-win32-src.zip
httpd-2.2.3.tar.gz
and the NOTICE files are tied to the source tree (httpd).
Isn't the whole problem
Let me sugest:
:: Nahche ::
Nahche (Na-ai-che, `mischievous,' `meddlesome.'-George Wrattan). An
Apache warrior, a member of the Chiricahua band. He is the second son
of the celebrated Cochise, and as hereditary chief succeeded his elder
brother, Tazi, on the death of the latter. His mother was a
On Friday 28 July 2006 22:59, Jorge Schrauwen wrote:
Let me sugest:
:: Nahche ::
Nahche (Na-ai-che, `mischievous,' `meddlesome.'-George Wrattan). An
Apache warrior, a member of the Chiricahua band. He is the second son
of the celebrated Cochise, and as hereditary chief succeeded his elder
Nick Kew wrote:
Isn't the whole problem the lack of a proper product name that
we or anyone can identify with (other than Apache)?
With that in mind, how about something more distinctive and
less ineffably lame than anything like httpd or web server?
For example, draw on our heritage and
I wouldn't push the "Apache" thing.
Truth is... a letter could show up at any moment from lawyers
of the Apache Nation regarding the name usage.
Might even be way overdue.
I wouldn't "go there" and draw attention to the issue at all.
Yours...
Kevin Kiley
In a message dated 7/28/2006
Jorge Schrauwen wrote:
Let me sugest:
:: Nahche ::
Nahche (Na-ai-che, `mischievous,' `meddlesome.'-George Wrattan). An
Apache warrior, a member of the Chiricahua band. He is the second son
of the celebrated Cochise, and as hereditary chief succeeded his elder
brother, Tazi, on the death of
Fair point you have there...
As long as the new name isn't some way to hard to rememebr abrivation :)
AMPES ;) Apache Multi Protocal Extenable Sever j/k
On 7/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I wouldn't push the Apache thing.
Truth is... a letter could show up at any
On 07/29/2006 12:30 AM, Brad Nicholes wrote:
There is a new concept (directive) that has been added to the
authorization (access control) portion of the web server. This new concept
is reject. Basically what this directive does is allow you to specify
conditions by which access or
Apache HTTP Server is (mostly) a web server.
Let's call it 'parker'
(I'll let the Spider Man fans explain it... :) )
--
===
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
If you can
just a heads up:
does not exist
http://httpd.apache.org/apreq/docs/libapreq2/examples.html
still no perl
http://httpd.apache.org/apreq/docs/libapreq2/group__apreq__lang.html
Jim Jagielski wrote:
Many compile warnings when compiling with maint-mode:
Fixed. Thanks,
Cheers
Jean-Frederic
mod_proxy.c: In function 'add_pass':
mod_proxy.c:1176: warning: implicit declaration of function
'proxy_checkstorage_add_entry'
mod_proxy.c: In function 'proxy_post_config':
Davi Arnaut wrote:
Em 28/07/2006, às 13:34, [EMAIL PROTECTED] escreveu:
Author: jfclere
Date: Fri Jul 28 09:33:58 2006
New Revision: 426604
...
+
+static const slotmem_storage_method *checkstorage = NULL;
+static ap_slotmem_t *myscore=NULL;
Indentation consistency ? myscore=NULL
Ruediger Pluem wrote:
On 28.07.2006 18:34, [EMAIL PROTECTED] wrote:
Author: jfclere
Date: Fri Jul 28 09:33:58 2006
New Revision: 426604
URL: http://svn.apache.org/viewvc?rev=426604view=rev
Log:
First try to put togother an external health checker for mod_proxy.
Modified:
A quick check shows that various worker stats are not shared...
doing a reload of the balancer-manager shows the I/O/Elected
values flopping all over the place. So they seem in this
impl process specific and not shared at all. Did nothing
special to build modules/mem just allowed default config
I'm looking into converting a mass virtualhost cluster from zeus to apache
and I can't find a secure way to do this. I'm considering only mod_vhost_alias
because I currently have 20,000 domains hosted on a few dozen servers connected
to a NFS NAS. A hardcoded configuration is not practical in
Folks,
On FreeBSD servers with accept filtering enabled, the nntp-like tests
in perl-framework hang because the client expects the server to send
data first, and the server never gets the request because it hangs in
the accept filter until the client sends data (which it doesn't).
As
[ http://issues.apache.org/jira/browse/MODPYTHON-164?page=all ]
Graham Dumpleton reassigned MODPYTHON-164:
--
Assignee: Graham Dumpleton
Allow req.add_handler()/req.register_*_filter() to take module/function for
handler.
[ http://issues.apache.org/jira/browse/MODPYTHON-164?page=all ]
Work on MODPYTHON-164 started by Graham Dumpleton.
Allow req.add_handler()/req.register_*_filter() to take module/function for
handler.
43 matches
Mail list logo
