--On Wednesday, March 5, 2003 8:48 PM -0800 Ian Holsman <[EMAIL PROTECTED]>
wrote:
I'm +1 on this as well.
so.. whats the procedure to get this committed into the
experimental/auth area?
As I said before, I don't believe these auth modules should be in the core -
the people who are so interested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dirk-Willem van Gulik wrote:
|
| On Tue, 4 Mar 2003, Paul Querna wrote:
|
|
|>so. What does everyone thing about including this in apache-2.1?
|
|
| Though a separate auth module tree was discussed for things like this -
| note that this module is very
APACHE 2.1 STATUS: -*-text-*-
Last modified at [$Date: 2003/02/24 00:00:05 $]
Release [NOTE that only Alpha/Beta releases occur in 2.1 development]:
2.1.0 : in development
Please consult the following STATUS files for information
on related proj
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2003/02/04 19:08:59 $]
Release:
1.3.28-dev: In development
1.3.27: Tagged September 30, 2002. Announced Oct 3, 2002.
1.3.26: Tagged June 18, 2002.
1.3.25: Tagged June 17, 2002. Not re
Hello,
JS>The long answer: using downgrade-1.0 will, in fact, force Apache to treat
JS>the request as if it was HTTP/1.0. It will therefore use only HTTP/1.0
JS>features in the response. But it will still respond with HTTP/1.1 in the
JS>response line, since this just declares it as an HTTP/1.1 c
[This question seems more appropriate for the users list rather than
the developers list.]
On Wed, 5 Mar 2003, Andrew Ho wrote:
> I am dealing with a broken proxy which understands chunked
> Transfer-Encoding on the proxy to server side, but does the wrong thing on
> the proxy to client side (it
Hello,
I am dealing with a broken proxy which understands chunked
Transfer-Encoding on the proxy to server side, but does the wrong thing on
the proxy to client side (it sends the "Transfer-Encoding: chunked" header
from the server to proxy response, but sends the content unchunked).
The easiest
* Greg Ames ([EMAIL PROTECTED]) wrote :
> I mentioned this to other Apache folks around here and got some interesting
> reactions:
>
> * If we don't control this with a directive, we might violate the rule of
> least astonishment. For example, admins might be living with some buggy
> modules,
On APACHE_2_0_BRANCH, I'm seeing this compiler warning on RedHat 8.0.94 using
gcc 3.2.2 with openssl-0.9.7-6:
/bin/sh /export/home1/blair/Code/Apache/2.0/h/srclib/apr/libtool --silent --mode
=compile gcc -pthread -g -O2 -I/usr/kerberos/include -Wl,-rpath,/opt/i386-linu
x/db-4.1/lib -DLINUX=2 -D
I've never had much luck getting coredumps on Linux after a seg fault or
whatever when I start the server as root. My usual procedure was to recreate
the problem with httpd started as non-root, get a coredump, then debug the problem.
Recently I found out that some of my httpd's were seg faultin
Currently "CachEnable foo / " will configure mod_cache to cache all forward proxy
responses. Seems to me we want to be a little more granular than that.
The following patch will enable the use of e.g. "CacheEnable foo http: "
to signify that just HTTP content should be cached. It also will allow
sc
+AP_INIT_TAKE1("WindowsSocketsWorkaround", set_sockets_workaround, NULL, RSRC_CONF,
+ "Set \"on\" to work around buggy Winsock provider implementations of certain VPN or
Firewall software"),
+
hey, no need to double code. AP_INIT_FLAG exists ;-)
Well I guess that's just a matter of personal
* [EMAIL PROTECTED] wrote:
> +AP_INIT_TAKE1("WindowsSocketsWorkaround", set_sockets_workaround, NULL, RSRC_CONF,
> + "Set \"on\" to work around buggy Winsock provider implementations of certain
> VPN or Firewall software"),
> +
hey, no need to double code. AP_INIT_FLAG exists ;-)
nd
--
On Tue, 4 Mar 2003, Paul Querna wrote:
> so. What does everyone thing about including this in apache-2.1?
Though a separate auth module tree was discussed for things like this -
note that this module is very database agnostic - and I'd argue that it
may be good for the base distribution.
Dw.
14 matches
Mail list logo
