So, when I volunteered to integrate mod_pop3 I thought I would have to do
some modifications to the code to bring it up to date, but that is not the
case.
I tested it over the weekend both in Apache 2.0 and Apache 2.1 and
compiles and works just fine.
If people decide to include it in
I'd like to integrate it. I guess the best location for now is experimental/ ?
Moving to closure on the decision - my sense is that this plan is
acceptable.
Now we can transition to doing the deed. Anybody got enough of an itch
around that code to rescue it?
I'll advocate retiring it
On Thu, Oct 03, 2002 at 03:22:35AM +0200, André Malo wrote:
http://httpd.apache.org/docs-2.0/mod/core.html#rlimitnproc says:
| Note: If CGI processes are not running under userids other than the
| web server userid, this directive will limit the number of processes
| that the server
On Mon, Jul 22, 2002 at 06:04:42AM -0700, Sylbert L wrote:
Hi,
Can anyone suggest some good reading material or some resources that could
help me out with modifying apache code / developing an apache module? So far
I've been trying to understand whats going on by reading the code itself
On Fri, May 31, 2002 at 11:26:55AM +0100, Matt Kern wrote:
There is a feature I have wanted in Apache for a little while now: the
ability to preserve the host header when using mod_proxy. This is
mostly useful for two (or more) tier systems, where it is desirable to
pass certain virtual
http://httpd.apache.org/docs-2.0/developer/
Most people do not need to modify the server itself, but rather just write a
module. In that case pick one of the simple ones that come in the
distribution and see how things work.
Have a look at Doug MacEachern's Writing Apache Modules with mod_perl
Comanche works fine with Apache 2.0 as well.
mod_perl has supported 2.0 for as long as I can remember, in fact it was the
first major module to do so and take advantage of the new threading
capabilities.
Daniel
From the daily digest posting of freshmeat, I learned that a new
version of
Comanche works fine with Apache 2.0 as well.
mod_perl has supported 2.0 for as long as I can remember, in fact it was the
first major module to do so and take advantage of the new threading
capabilities.
As far as I know, Comanche is not webby (i.e. web interface), but
tcl/tk.
I
It is possible with HTTP/1.1, just not implemented
http://www.ietf.org/rfc/rfc2817.txt
I know that the docs say it's not possible, but is it theoretically
possible?
No. Not with SSL, at least.
http://www.modssl.org/docs/2.8/ssl_faq.html#ToC47
minfrin 02/03/22 10:34:46
Modified:.CHANGES
modules/http http_protocol.c
Log:
When a proxied site was being served, Apache was replacing
the original site Server header with it's own, which is not
allowed by RFC2616. Fixed.
This may be
Just for the record, it seems someone already saw the tarball and posted it to
freshmeat.
http://freshmeat.net/releases/69982/
Design and implementation of Apache 2.0 is nearing completion. Module
authors are encouraged to review the Apache 2.0 API and share any
concerns with the Apache
This question should be directed to the [EMAIL PROTECTED] list
You need to add the following:
AddType application/x-httpd-php .php
Daniel
On Mon, Feb 04, 2002 at 05:20:25PM -0500, David Ford wrote:
What does apache2 need in httpd.conf to properly shunt php files through
the php engine
On Thu, Dec 20, 2001 at 11:07:13AM -0800, Doug MacEachern wrote:
On Thu, 20 Dec 2001, Daniel Lopez wrote:
/dev/urandom is not available in all platforms
right, which is why it is not portable to use directly.
I was not arguing, I was just reinstating your point :)
On NT openssl uses
I am trying to make sense of the following directives:
MaxClients, ServerLimit, ThreadLimit, ThreadsPerChild
As I understand:
MaxClients = ServerLimit in prefork
ThreadsPerChild = ThreadLimit
MaxClients = Serverlimit * ThreadLimit in worker
Can be MaxClients and ThreadLimit eliminated?
Ok, now it makes sense :) I suggest your explanation gets
added to the docs and linked as a See also for all the directives involved.
Cheers
Daniel
---
Sure, but...
Here is how I would have them configured with prefork:
MaxClients: big enough to handle normal, expected load
mod_proxy it adds additional headers like X-Forwarded-For ,
X-Forwarded-Host, X-Forwarded-Server in the content handling phase that
I may want to modify, replace or unset.
In this case a ProxyAddOutputFilter directive could be used to add the
mod_headers filter, this will do this for
Apache could pass this information in an HTTP request, no need for a special
protocol.
And dinamically reconfigure your apache web server from an HTTP request? I
don't really see how... Like, if I know that /examples/*.jsp is something
that need to be processed by a Servlet, and
mod_headers allows modification of headers between client and apache, but
not headers between proxy and origin server.
Read the following section of the mod_headers manual to find out how to
change the request headers before they are passed to the remote server:
On Sat, Oct 20, 2001 at 11:16:10AM +0200, Graham Leggett wrote:
Daniel Lopez wrote:
I need an additional hook to process headers before they are sent to the
origin server in a reverse proxy configuration.
Use mod_headers for this - it was modified to handle this behavior a
while back
Hi
I need an additional hook to process headers before they are sent to the
origin server in a reverse proxy configuration.
Please consider the following patch.
Best regards
Daniel
PS: This is for proxy for Apache 2.0, unsure about if it belongs on modproxy-dev
or here.
--
[EMAIL
20 matches
Mail list logo
