[EMAIL PROTECTED] wrote:
The 'other' not-so-dedicated-but-certainly-interested
developers felt 'shut out' of the 2.0 development cycle
because it was obvious a lot of it was taking place
'off line' and nothing was being documented so they
couldn't really get a good handle on what was going
on in
Rasmus Lerdorf wrote:
I also work for a large company with plenty of talented developers and
thousands of production Apache-1.3 servers along with hundreds of custom
Apache-1.3 modules. It will be years before I can even consider Apache2,
given the architecture and API differences between the
[EMAIL PROTECTED] wrote:
--
FACT?: Apache 2.0 pre-fork ( which is the only thing still available on
some of the best platforms ) is SLOWER than Apache 1.3 pre-fork.
--
This gives someone who might be stuck with one of those pre-fork
only platforms, or anyone who just WANTS to stick with
Jim Jagielski wrote:
Look at the impact of not having 2.0 modules severely
limited the acceptance of 2.0. Not having 1.4 modules
will most certainly do the same*. If 1.4 == 1.3,
binary-wise, then it's a non-issue; if not, it's
a *major* issue.
* Yes, part of the delay was due to porting, which
Dmitri Tikhonov wrote:
ap_proxy_canonenc() encode tilde into hexadecimal format before issuing
HTTP request. This breaks some things for me. Why is it not allowed in
its original form? I modified the source (2.0.46) of proxy_util.c, and it
works fine.
- Dmitri.
--- proxy_util.c
Hi all,
I am having a hassle with a server running httpd v2.0.47 in that it
refuses to restart cleanly after an unclean shutdown. Before Apache will
start again, the SSL session cache file needs to be manually deleted.
Is this problem still around in v2.0.49, in other words is an upgrade
g g wrote:
[EMAIL PROTECTED] bin]$ ./apachectl start
[Tue Mar 23 05:13:54 2004] [warn] Loaded DSO /home/app6/abc.so uses
plain Apache 1.3 API, this module might crash under EAPI! (please
recompile it with -DEAPI)
The above line is probably what is wrong - your module needs to be
compiled with
Peter Van Biesen wrote:
I created the directory ldapCache under the serverroot and restarted the
server. The file sharedCacheFile was created, but with owner root, while
the server itself runs under sysadm user ( but apachectl is run by root,
to be able to bind to port 80 ) . Anyways, the
Brad Nicholes wrote:
But my guess
is that this patch should significantly help to resolve the problem that
you are seeing.
I'll give it a whirl on the problem server, and get back to you whether
it fixes it or not.
Regards,
Graham
--
[EMAIL PROTECTED] wrote:
Modified:modules/experimental util_ldap.c
Log:
if the call to ldap_simple_bind_s() fails, the connection is left in an unbound
state. Make sure that the connection record is updated to show the current state.
I have been having a problem with auth_ldap in that
Hi all,
I've been having some odd behaviour from mod_auth_ldap, wondering if
anybody else has come across this.
If you configure basic authentication against LDAP, it seems to work
fine. You can log in with a correct password, and it lets you in. You
can log in with an incorrect password, it
Igor Sysoev wrote:
mod_accel ( http://sysoev.ru/en/ ) allows to take cookies into account while
caching:
AccelCacheCookie some_cookie_name another_cookie_name
You can set it on per-location basis.
Besides, my upcoming light-weight http and reverse proxy server nginx
will allow to do it too.
Hi all,
I am busy researching the idea of an Apache + DAV server that would do
the job of what a typical Samba server does now - file sharing. An
Apache server would have the advantage of native SSL support, flexible
authentication configuration, etc.
One thing I would like to be able to do
Greg Stein wrote:
Eesh. This has tended to come up w.r.t mod_dav for over five years now. My
point of view is best summarized in this email:
http://mailman.lyra.org/pipermail/dav-dev/2000-November/001746.html
I really don't recommend it. Why do you need to have different owners for
the files?
Joshua Slive wrote:
If you really want apache to behave like samba, then I suppose you don't
mind if apache runs as root. Then it becomes rather more simple to do the
sort of things you are interested in. It also becomes rather more simple
to compromise your box.
If I don't run Apache, then I
André Malo wrote:
Hmm. I suspect, the difference is, that Apache was never designed to run as
root.
You're assuming the root account is the most damaging account to
compromise. In the case of a fileserver, you will very likely want some
files kept more private than others. If I as a hacker
Neil Gunton wrote:
The problem now is that the browsers (IE and Mozilla at least) don't
seem to differentiate requests based on cookies. I have tested
requesting a page with a certain cookie (where the page has a sufficient
expiration to warrant being cached for the duration of the test), and
Neil Gunton wrote:
Is this really such a special case? I can't believe nobody else has
wanted to implement a server like this.
It's a special case in the context of all of the servers, proxies,
transparent proxies and browsers together out there on the net - it's
useful to take off the load of
Hi all,
I have just installed the latest published version of httpd (v2.0.49),
and the problem where httpd refuses to start unless the file
ssl_gcache_data is manually deleted beforehand is still there.
I recall some recent discussion about the problem, but don't know if a
fix ever got into
Roy T. Fielding wrote:
I do wish people would read the specification to refresh their memory
before summarizing. RFC 2616 doesn't say anything about cookies -- it
doesn't have to because there are already several mechanisms for marking
a request or response as varying. In this case
Vary:
Hi all,
There is a request outstanding for the ability to specify the trusted CA
for TLS on a per virtualhost basis.
With openldap, the TLS setting can be set per connection with the
ldap_set_option() function. I don't have info for the ways that the
Netscape, Netware or Microsoft SDKs work -
Hi all,
I have just tried to build v2.0.49 under RHEL3, and I get the failure below.
For some reason, Redhat put krb5.h inside /usr/kerberos/include, and if
the include path /usr/kerberos/include is not added to CFLAGS, none of
the ssl stuff will compile (as ssl.h includes krb5.h). Is it
Aryeh Katz wrote:
I have just tried to build v2.0.49 under RHEL3, and I get the failure
below.
I had the same failure w RH9
see
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18989
Aryeh
For some reason, Redhat put krb5.h inside /usr/kerberos/include, and
if the include path
Brad Nicholes wrote:
My feeling is that about the best we could do is to allow the
LDAPTrustedCA and LDAPTrustedCAType directives to be callable from
within a virtualhost configurtion and keep a list of certificates that
can then be passed to the LDAP libraries during the post_config. But
this
Hi all,
I have just tried to build a test tree of the most recent v2.0.50-dev,
and it broke like this:
/home/gatekeeper/minfrin/src/apache/sandbox/proxy/httpd-2.0/srclib/apr/libtool
--silent --mode=compile gcc -g -O2 -pthread-DLINUX=2 -D_REENTRANT
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE
Hi all,
The outstanding bugs for mod_ldap* in Bugzilla have gone from 38 down to
9 - single figures at last.
There are 4 open segfault bugs - can y'all give the code a bit of a
hammering to see if there are any gotchas left un-stomped-on.
Regards,
Graham
--
Joseph Dane wrote:
essentially, I'd like to be able to set a maximum lifetime for a
persitent LDAP connection. an approximation of this would be to
record the time at which a connection was first made, and on
recycling the connection first check if that time was N seconds ago,
and unbind/rebind
William A. Rowe, Jr. wrote:
I have just tried to build a test tree of the most recent v2.0.50-dev, and it broke
like this:
config.c:1587: `FNM_PERIOD' undeclared (first use in this function)
Attempting to build against APR 1.0?
The httpd tree was whatever was the latest v2.0 CVS, and the
Paul Querna wrote:
This would be an interesting application of the AuthN framework stuff in
2.1.0. It is much easier to setup fallback authentication stuff.
Speaking of that, Is there any reason mod_auth_ldap hasn't been moved
over to the AuthN/Z Framework?
I think partly because nobody has
Hi all,
The above bug was posted about LDAP support not building on Solaris due
to ldap.h and lber.h being declared in the wrong order.
This patch has been committed to apr-util v1.0, what needs to be done to
get it committed to apr-util v0.9?
Regards,
Graham
--
---
Hi all,
I am having a moment: I am trying to build httpd statically, but I'm
struggling to find out how it is done.
The ./configure script can be configured to build all binaries
statically using --enable-static-[binary], except for httpd for some reason.
Can anyone tell me how it is done?
Hi all,
There have been a number of outstanding bug reports on proxy concerning
mod_proxy and URLs that have %xx escaping in them.
For proxy's internal use, it would need to remove the escaping of the
URL so that a request for http://whatever/%65 and a request for
http://whatever/A would be
Mathias Herberts wrote:
What is the position of the Apache community on the passing of 'hop by
hop' headers to origin servers by mod_proxy? The code in proxy_http.c
says 'RFC2616 13.5.1 says we should strip these headers', but RFC 2616
13.5.1 defines 'Hop-by-hop headers, which are meaningful
Jess Holle wrote:
On UNIX?
See the bug for what details I managed to muster at some point.
Can you point out which bug, there were lots that I opened and closed, I
just want to make sure I didn't close a bug that should be still open.
Regards,
Graham
--
Jess Holle wrote:
My feedback was mainly attached to bug #18756
http://issues.apache.org/bugzilla/show_bug.cgi?id=18756. This bug is
still present in 2.0.49. I do not know if it is a true duplicate as
indicated or not. I just know it does not work.
I also had reported 24801
Sumeet Singh wrote:
I would think that mod_proxy should make an independant decision (based
on compliance with the RFC, mod_proxy's configuration, type of origin
server etc) on whether it should send a chunked or dechunked request
body. For example, if the client sent chunked data that was
John wrote:
Dagone spam filtering, this patch never made it to the
list. Well I'll send it again, from a different e-mail..
So, here's the patch that fixes it for Netscape/Mozilla,
and whatever other browsers work similarly.
--- proxy_ftp.c 2004-05-28 15:15:15.960934000 -0400
+++ proxy_ftp.c.new
Brad Nicholes wrote:
But if you are allocating memory for cache entries that are
constantly expiring and being purged, the pool will continue to grow
until the server is restarted. The pool would end up with stale memory
that the system has no way of reclaiming outside of restarting the
Brad Nicholes wrote:
I guess that is a possibility but I still don't understand what the
problem is with using calloc() and free() for the ldap caching code.
This seems to be a common thing to do when global memory needs to be
allocated and deallocated constantly. To avoid having the memory
Brad Nicholes wrote:
At least on NetWare, switching to pools would make the code much
more complex. Rather than simply calling calloc and free in the same
way that we are calling apr_rmm_calloc() and apr_rmm_free(), we would
have to implement essentially the same model using pools and
Brad Nicholes wrote:
Do we even know that there is a problem with this code? I haven't seen
any memory leaks so far. I would hate to go to all of the work to
redesign and rewrite the ldap_cache manager for little to no gain.
It does not seem to handle the we ran out of memory while trying to add
Brad Nicholes wrote:
It appears to me that if it doesn't handle low memory situations or
it is giving false positives, those are separate issues from pools vs.
calloc/free. I still think we need to implement some better monitoring
or logging code in the cache_mgr and enhance the cache-status
[EMAIL PROTECTED] wrote:
bnicholes2004/06/11 09:15:43
Modified:.Tag: APACHE_2_0_BRANCH CHANGES STATUS
modules/experimental Tag: APACHE_2_0_BRANCH util_ldap.c
Log:
Allow relative paths for LDAPTrustedCA to be resolved against ServerRoot PR#26602
Have the docs
Brad Nicholes wrote:
Do the docs need to be updated for this change? Allowing relative
paths to be resolved against ServerRoot seemed like fairly standard
procedure.
Looking at the docs there now, I think you're right. Just wanted to
check whether there was anything that implied an absolute
Guernsey, Byron (GE Consumer Industrial) wrote:
Don't expect a quick response. I submitted a feature patch to bugzilla over a month ago and it hasn't changed state from its new state or had any activity or ownership changes. I posted a followup message here a few weeks later and have not
Sander Striker wrote:
My second attempt at preparing a 2.0.50 rc tarball...
I've tagged the tree (STRIKER_2_0_50_RC2) and uploaded associated
tarballs to:
http://httpd.apache.org/dev/dist/
Please test and report.
The tarball refuses to build as an RPM.
The attached patch fixes this.
I need one
Jeff Trawick wrote:
--- build/rpm/httpd.spec.in2004-02-07 20:44:30.0 +0200
+++ httpd.spec.in2004-06-24 19:25:19.0 +0200
@@ -17,7 +17,7 @@
License: Apache License, Version 2.0
Group: System Environment/Daemons
BuildRoot: %{_tmppath}/%{name}-root
-BuildPrereq:
William A. Rowe, Jr. wrote:
Graham, silly question. When it deploys as an RPM, do we also copy
LICENSE and NOTICE to some appropriate spot? This tripped me in
the latest updates - was moving the LICENSE and not NOTICE in the
time since that second file was introduced.
Just checked: Neither our
William A. Rowe, Jr. wrote:
Heh, maybe they don't. In the win32 installer and build system we drop them
into the target directory, alongside the bin, htdocs, modules directories.
On unix, we do toss LICENSE into $target/manual/ - but we are missing
NOTICE in the build system. Perhaps that's the
Jesse Kielthy wrote:
Do you know a reason why there is a 3MB peak at the
start? Is it something to do with Server set-up
connection requirements?
The 3MB peak is probably caused by your test running over a fast network.
Apache will send as much data as your client is willing to receive, and
in
William A. Rowe, Jr. wrote:
Refer to http://www.apache.org/dev/apply-license.html --- especially;
To apply the ALv2 to a new software distribution, include one copy of
the license text by copying the file:
Nick Kew wrote:
(2) Bug #29554 - URL munging
I've ported Francois-Rene Rideau's patch to 2.1, subject to the
question over proxy_fixup discussed in my last post.
Looking at this issue, I think the real solution is to
a) canonicalise all URLS (reverse and forward) for internal Apache use.
b) use
Nick Kew wrote:
Can anyone see why proxy_fixup should not be removed altogether?
Proxy fixup seems to do the job of making sure the URL /%41%42%43
matches ProxyPass /ABC http://xxx/ABC;, so I don't think it should be
removed altogether.
The URL that is sent to the backend server however has no
[EMAIL PROTECTED] wrote:
+#if APR_HAS_SHARED_MEMORY
+/* If the cache file already exists then delete it. Otherwise we are
+ * going to run into problems creating the shared memory. */
+apr_file_remove(st-cache_file, ptemp);
+if (st-cache_file) {
+
Brad Nicholes wrote:
No, I didn't change anything that would allow for anonymous shared
memory. This should probably check for a NULL before calling
apr_file_remove().
+apr_file_remove(st-cache_file, ptemp);
Will this line segfault if ptempt is NULL? If not, then it should be
fine.
[EMAIL PROTECTED] wrote:
Check for a NULL file name before trying to delete the file
Is this in STATUS?
Regards,
Graham
--
Brad Nicholes wrote:
I'm not sure what you are asking. I haven't proposed any of my
recent changes for backport yet because of the changes required in
include/util_ldap.h. Since util_ldap.h can be considered a public
header, technically any changes to the structure would require an MMN
bump.
Brad Nicholes wrote:
I was hoping to avoid the MMN bump mainly because that means we can't
backport the changes to the 2.0 branch. If the httpd 2.2 includes a
caching_util module then the only reason for these stabilization patches
is the 2.0 branch. Also, if there are any other modules that do
Sander Striker wrote:
The 2.0.50 tarballs are up and available for testing at:
http://httpd.apache.org/dev/dist/
Please test and cast your votes for release.
The trivial fix to make the above file build as an RPM is still
outstanding, and requires one more +1 to apply it.
Any takers?
Regards,
Chip Cuccio wrote:
The trivial fix to make the above file build as an RPM is still
outstanding, and requires one more +1 to apply it.
I built RPMs with no issues for Fedora and RH 7.2 - 9.0.
Are you referring to the libpcre hack?
No, I am referring to the spec file included in httpd v2.0.50,
Chip Cuccio wrote:
Ahhh - thanks ;-)
Shall I take a crack at it? How can we test the resultant spec?
The diff is attached - give it a try, tell me if it works. You need to
run ./buildconf to generate the httpd.spec from build/rpm/httpd.spec.in,
then tar up the archive and run
rpmbuild --rebuild
Joe Orton wrote:
If it just fails due to the unpackaged files check that's hardly a
showstopper, just do:
echo %_unpackaged_files_terminate_build 0 ~/.rpmmacros
You're asking end users to issue an arcane command to work around a bug
in the Apache supplied specfile. The real fix is to fix the RPM
Ian Holsman wrote:
your welcome.
Thank you kind sir :)
Regards,
Graham
--
Hi all,
I have built binary RPMs for i386 and ppc of httpd-2.0.50. In order to
get the RPMs to build at all, I used the RPM spec file that includes the
missing files fixes + db4-devel change included in v2.0.51-dev against
the standard httpd-2.0.50-tar.gz archive as released.
Should these
Hi all,
Where do historical binaries get moved to (if anywhere)?
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Signature
Joshua Slive wrote:
Ahhh Make that
http://archive.apache.org/dist/httpd/binaries/
Found it, thanks.
And note that the moving is automatic: everything from
www.apache.org/dist/ goes there automatically, and nothing is ever
deleted.
Automatic as in a script does it? I just moved the old release
Sander Temme wrote:
Well, the only delta is the SPEC file, right?
Correct.
How about publishing your
RPMs, pointing out that they represent a small delta w.r.t. the 2.0.50
tag, and rolling a patch representing those changes?
That way, we have viable RPMs available, and if folks want to roll
Jess Holle wrote:
Bug 24801 is still present in Apache 2.0.50. [See my additional notes
in the report.]
And the stuff that landed in v2.0.51-dev? There is an overhaul of
locking in there that has potentially fixed a lot of problems.
Remember that bug 24801 doesn't describe a discrete bug, but
Ian Holsman wrote:
ok, now before I start this let me say one thing, this is not for *ALL*
requests, it will only work for ones which don't have content-length
modifiable filters (like gzip) applied to the request, and it would be
left to the webserver admin to figure out what they were, and if
Sadaf Alvi wrote:
i saw util_ldap_cache to know from which pool it is allocating cache
memory. i wonder to know that it is using util_ldap_cache_mgr which in
turn using calloc free internally.
why it is not using pconf pool to allocate cache memory?? is there
any memory or performance issue ??
Nick Kew wrote:
That will not always be practicable. mod_proxy should be configurable
to pass byteranges headers straight through to the backend or strip them
and assume the proxy will handle the ranges.
Byte ranges are a part of HTTP/1.1, and mod_proxy claims to be an
HTTP/1.1 proxy. mod_proxy
Jess Holle wrote:
I've not tested 2.0.51-dev yet -- as 2.0.50 just came out a short while
ago...
There was a big change to the LDAP stuff that was landed after 2.0.50
shipped, there were questions about whether an MMN bump was needed, thus
the holdoff till v2.0.51.
I do not believe this
Geoffrey Young wrote:
while I'm all for reducing server overhead (who isn't :) playing these kind
of games with the filter API seems like such a bad idea. what we have now
is a modular design that is simple and works - content handlers generate a
response, while various filters adjust that
Joe Orton wrote:
As far as I can tell the byterange filter should handle all such cases
correctly already: read ap_set_byterange() - it punts on a non-200
r-status or when r-headers_out contains a Content-Range header etc.
Is this side-discussion just theoretical pondering or is there some real
Joe Orton wrote:
Yes, that's exactly what it's supposed to do already. I haven't checked
that it works via the proxy but it certainly does for other cases.
Ok, then most of the problem is solved :)
The full 650MB CD ISO is then transferred from the backend to the
frontend, which then pulls out
Geoffrey Young wrote:
please take the rest of this as just a friendly discussion - I don't want it
to turn into some kind of bickering match, since that's definitely not what
I have in mind :)
Cool no problem - it's quite a complex thing this, and I was struggling
trying to make it clear what
William A. Rowe, Jr. wrote:
The solution to this problem is *not* to become tightly coupled with the
placement of filters, directly handling file streams, etc.
The clean solution is a new forward-space semantic for the filter or
brigade, which would allow you to skip n bytes. This would allow
Nick Kew wrote:
Indeed. In a straight-through proxy that's right.
But in the case of a cacheing proxy, it may be better for it to retrieve
the entire document and manage byteranges locally. And in the case of
a content-transforming proxy, the filters may need the entire content to
function at
William A. Rowe, Jr. wrote:
I don't like where this conversation is heading at all. You are suggesting that
every filter needs to become progressively more aware of the http module
characteristics, but that's what we were moving away from in apache 2.0.
Ok, this is exactly how Geoffrey Young
joon yang wrote:
I'm trying to add group authorization to mod_cas, but
want to use ldap entry.
I started tinkering with using the util_ldap.c 's
util_ldap_cache_compare() function. Does anyone have
any experience tinkering with util_ldap.c in apache?
Use the mod_auth_ldap module as example code
CHOU,TAIR-SHIAN (HP-Cupertino,ex1) wrote:
AuthLDAPURL ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius
require valid-user
When I try the above AuthLDAPURL example given in Apache Module
mod_auth_ldap document with 2.0.50, I get the following error:
Syntax error on line 19 of
Pier Fumagalli wrote:
I don't understand why mod_cache forcedly avoids caching URLs ending
with the / (slash) character.
Apparently EGP (who's he?) agrees.
Anyhow, it's several months that we're running with this patch in
production, and nothing bad seems to be happening.
If it works, I say
Brian Akins wrote:
If it works, I say commit the patch. Can think of no reason why we
should not cache an URL ending is /.
Because the cache_in filter gets added in the quick_handler. The
fast_internal_redirect in mod_dir which translates / to /index.html (or
whatever) seems to lose this
Henri Gomez wrote:
And what about using AJP/1.3 instead of HTTP for connection to tomcat ?)
In all my deployments of tomcat I have never seen the point of a custom
protocol that did exactly what HTTP does, so all my tomcat deployments
are all HTTP, with a simple mod_proxy frontend.
Even the get
Henri Gomez wrote:
jk was designed a long time ago so may be mod_proxy allready support
persistant connections.
Persistence will happen on the backend on the condition there was
persistence on the frontend. Generally the networks between backend and
frontend are fast enough that connection setup
Henri Gomez wrote:
It's now time to refactor and redesign it with Apache 2.x (APR/AP) in
mind to follow Apache 2.x admins habbits and try to make something
simpler.
We came on httpd-dev for advice from experts, and may be an
extended mod_proxy could be the solution. But we also want to keep
the
Manni Wood wrote:
One of the things I thought AJP did that HTTP proxying to Tomcat could
not (but correct me here if I'm wrong) is let the servelt container know
whether or not the connection is HTTP vs. HTTPS. This sort of
information needs to get passed back to the servlet container to satisfy
Henri Gomez wrote:
Well let see my suggestion :
ProxyPass /myWebapp/*.jsp ajp://myajpworker/
myajpworker is not a machine but a virtual resource which could be :
- a physical Tomcat using its AJP/1.3 connector
- a cluster of physical Tomcats using their AJP/1.3 connector
And via AJP/1.4 we could
Manni Wood wrote:
The real trick is getting Apache to serve all of the static content, and
getting tomcat to deal with only servlets and jsps.
As has been pointed out, mod_rewrite can do this already.
I notice in all of the documentation I find for mod_jk, an entire
directory (/examples/* being
Henri Gomez wrote:
- mod_proxy + proxy_ajp could be one solution.
Now what about the mod_proxy load-balancing add-on ?
Would be a completely separate module.
The way proxy works, is that it:
- obtains the IP address to connect to (currently via DNS round robin,
but a module proxy_loadbalancer
Henri Gomez wrote:
And in fine if we could have proxy_ajp included in Apache 2.x
distribution, we'll a great step in Apache2/Tomcat integration,
which should be a goal for ASF members we are.
Having proxy_ajp included in httpd v2.0 would be a good thing - there is
a base of users for it (with
Colm MacCarthaigh wrote:
Using OPTIONS has the advantage of being backwards compatible, if you
send OPTIONS to a plain-old HTTP receiver, the standard ACK can be
taken to mean yep, I'm here. Intelligent backends (read: modify
tomcat and co slightly) can have an X-header or whatever to go
I'm
André Malo wrote:
Having proxy_ajp included in httpd v2.0 would be a good thing - there is
a base of users for it (with it's more advanced handling of things like
indicating secure connections, etc it's useful).
Hmm. I'd include rather in tomcat distribution than httpd-2.0. That seems to
be way
André Malo wrote:
Where's the user base of mod_imap (installed by default) or mod_cern_meta or
the old outdated NCSA config directives? We add and add and add code -- which
is not actually bad. But where's the man with the broom?
The issue of unmaintained code is an important issue, but not one
Mladen Turk wrote:
I don't think that it is necessary for a mod_ajp to be included inside the
mod_proxy, although they are sharing some common concepts.
I think it's very necessary - sharing those common concepts ultimately
makes for doing things in a consistent way. It makes a big difference to
Henri Gomez wrote:
BTW, could we expect to be able to use in proxy_ajp URL like
ajp://VIRTUALNAME, where VIRTUALNAME could be the name of an
AJP cluster backend ?
That would be up to proxy_ajp to decide, so yes.
What happens is that when the config says
ProxyPass /myApp ajp://VIRTUALNAME
and the
Mladen Turk wrote:
I think it's very necessary - sharing those common concepts
ultimately makes for doing things in a consistent way. It
makes a big difference to the usability of httpd.
I'm sure that the 'normalization' would lead to nowhere.
I don't follow - what does normalisation would lead
jean-frederic clere wrote:
I see in ap_proxy_http_handler() that DECLINED allows to try another. Is
there somewhere an example of a configuration using it?
ap_proxy_http_handler() is found in mod_proxy_http, which is the helper
module that handles the HTTP protocol in the proxy framework. You
Guernsey, Byron (GE Consumer Industrial) wrote:
We are using mod_proxy and a patched mod_rewrite to do sticky load balancing. Mod_rewrite
supports cookies, but not session based cookies. I added this
functionality and posted the
patch here (see mod_rewrite cookie patch (PR#28391))- still
Mladen Turk wrote:
The patch adds lb support in scoreboard, so that statuses for each lb worker
can be calculated for each child process.
It uses optional function to retrieve the number of lb workers and
calculates the scoreboard size accordingly.
Will applying this patch to httpd v2.0 require an
1 - 100 of 2225 matches
Mail list logo
