Graham Dumpleton (JIRA) wrote:
[ http://issues.apache.org/jira/browse/MODPYTHON-77?page=all ]
Graham Dumpleton updated MODPYTHON-77:
--
Attachment: grahamd_20051105.tar.gz
Here is my first go at an alternate patch for this problem. Patch was made
On 06/11/2005, at 2:42 AM, Jim Gallacher wrote:
The changes work fine on:
Mac OS X (10.3.9) / Apache 2.0.51 (worker) / Python 2.3 (Apple OS
Installed)
Linux Fedora Code 2 / Apache 2.0.55 (prefork) / Python 2.3.5
Test example was gilstate.tar.gz attached to MODPYTHON-77.
Also passed on
[
http://issues.apache.org/jira/browse/MODPYTHON-77?page=comments#action_12356864
]
Jim Gallacher commented on MODPYTHON-77:
Patched 3.2.4b with diff from grahamd_20051105.tar.gz. Unit tests and gilstate
test pass on Debian stable (sarge) and
On 06/11/2005, at 11:55 AM, Gregory (Grisha) Trubetskoy wrote:
On Sun, 6 Nov 2005, Graham Dumpleton wrote:
Haven't had a chance to investigate yet and ensure they aren't caused
by me
using versions of both Python and Apache not in standard locations.
Most
tests work though. The tests that
On Saturday 05 November 2005 07:33, Paul Querna wrote:
I believe that this is really a feature enhancement. It is not a
regression from the 2.0.xx branch. I don't believe it should be a show
stopper for 2.2.x.
Is this documented anywhere like bugzilla?
My gut feeling is that if it's not a
We have grown accustomed to two separate trust mechanisms
on the 'net; server certs signed by some authority, or the PGP
web of trust.
I would like to be able to use PGP trust over the web. That would
mean (something like) installing a certificate on the server, and
signing it with my PGP key.
Hi,
The whole point is I don't do compression because of any _clients'_
connections, but because of the _server's_ connection! If the server's
connection usually is far slower than the client's connection (like
with a server behind a V.90 modem, which would be 33.6 kb/s upstream
with
* Florian Zumbiehl wrote:
Hi,
The whole point is I don't do compression because of any _clients'_
connections, but because of the _server's_ connection! If the
server's connection usually is far slower than the client's
connection (like with a server behind a V.90 modem, which would
Hi,
I did not talk about traffic, but bandwidth. I read that you're concerned
about server's bandwidth and so it would be good if the clients get
uncompressed content from the cache rather than compressed from the server.
The trick to achieve both is *to deliver uncompressed content*
Nick Kew wrote:
We have grown accustomed to two separate trust mechanisms
on the 'net; server certs signed by some authority, or the PGP
web of trust.
I would like to be able to use PGP trust over the web. That would
mean (something like) installing a certificate on the server, and
To add a bit more detail to Ben's mail, OpenPGP:SDK is a new open
source library, available under a Apache-style license. It's a
completely new implementation of the OpenPGP spec, and is available at
http://openpgp.nominet.org.uk.
At EuroOSCon, we discussed a number of applications which could be
Sander Temme wrote:
On Oct 30, 2005, at 2:05 PM, Nick Kew wrote:
I'm just looking at docs/2.1 and noting some existing pages that
definitely
need updating. No reference to pages that need writing, or to non-
English
versions of anything. I might tackle some of these myself, but no
It's a bit more complex than that.
At a certain point, a fix was released for IE 6 to correct the
incompatibility that needed the 'ssl-unclean-shutdown' directive (I guess
it's KB 831167). At this point, we had two different flavours of IE+SSL
floating around.
Although we can determine if
Hello,
For both httpd-2.0.55 and httpd-2.1.8 there is a bug in
modules/dav/main/mod_dav.c. It is a null pointer dereference in some error
handling code, so I'm not surprised that no one has noticed this yet.
Look at line 2488 (in 2.0.55):
if (err != NULL) {
return dav_handle_err(r,
On 11/05/2005 09:42 PM, Ghassan Misherghi wrote:
Hello,
For both httpd-2.0.55 and httpd-2.1.8 there is a bug in
modules/dav/main/mod_dav.c. It is a null pointer dereference in some error
handling code, so I'm not surprised that no one has noticed this yet.
Look at line 2488 (in
On Saturday 05 November 2005 19:04, Joshua Slive wrote:
Sander Temme wrote:
I just upgraded www.apache.org to 2.1.9, and the main holdup was the
authn/authz modules... I'd put three stars *** next to some
documentation on upgrading a given 2.0 AAA configuration to its 2.2
equivalent.
The big reason that comes to my mind is that users don't want to have to
implicitly trust the server from the start, then register on the site by
uploading their own key before secure communications can begin.
The big advantage of a public certificate infrastructure is that the
rest of us can
On Saturday 05 November 2005 23:28, Phillip Susi wrote:
The big reason that comes to my mind is that users don't want to have to
implicitly trust the server from the start, then register on the site by
uploading their own key before secure communications can begin.
Why would anyone have to do
18 matches
Mail list logo
