-Original Message-
From: Joe Schaefer [mailto:joe_schae...@yahoo.com]
Sent: Dienstag, 8. Mai 2012 21:14
To: dev@httpd.apache.org
Cc: d...@httpd.apache.org
Subject: [VOTE] CMS site migration
Please cast your vote accordingly:
[X] : +1 to migrate httpd-site to the CMS
[ ] : 0
On Wed, May 9, 2012 at 6:26 AM, Paul Querna p...@querna.org wrote:
Heya,
A friend of mine is helping organizing the first C Conf:
http://www.cconf.org/
I think it could be a very interesting conference for those of us that
still enjoy coding C :-)
Not sure I can make it, but your friend
On 08 May 2012, at 9:14 PM, Joe Schaefer wrote:
Please cast your vote accordingly:
[X] : +1 to migrate httpd-site to the CMS
This is however with the condition that the process to update the CMS is
properly documented, and all stale documentation relating to the old way of
doing things is
The only significant workflow change is thatinstead of building
the docs you will need to publish them,either via the CMS site
or through the http://s.apache.org/cms-cliscript.
Nevertheless I'll update the README file in trunk with the full
details.
- Original Message -
From: Graham
Damned Y! loves to munge whitespace. The link is
http://s.apache.org/cms-cli
- Original Message -
From: Joe Schaefer joe_schae...@yahoo.com
To: d...@httpd.apache.org d...@httpd.apache.org; dev@httpd.apache.org
dev@httpd.apache.org
Cc:
Sent: Wednesday, May 9, 2012 6:34 AM
On 08 May 2012, at 9:14 PM, Joe Schaefer wrote:
Please cast your vote accordingly:
[X] : +1 to migrate httpd-site to the CMS
Since I'm the evil munchkin behind a lot of this, I should probably vote
as well. So there :).
Death to tables for styling html!
- Original Message -
From: Daniel Gruno rum...@cord.dk
To: dev@httpd.apache.org
Cc:
Sent: Wednesday, May 9, 2012 8:38 AM
Subject: Re: [VOTE] CMS site migration
On 08 May 2012, at 9:14 PM, Joe Schaefer wrote:
Please cast your vote
On Tue, May 8, 2012 at 3:14 PM, Joe Schaefer joe_schae...@yahoo.com wrote:
Please cast your vote accordingly:
[X] : 0 don't care one way or the other
Hi,
when setting ProxyErrorOverride to On to get the httpd-ErrorDocument
instead of the backend-errordoc, httpd is waiting ProxyTimeout seconds
to respond to the client, even though the response is already read from
backend server.
The request/response is hanging somewhere in
Hi Jim,
ok, that looks reasonable.
So it would make sense to introduce something like a prefix
directive for proxy_server_conf-id (e.g. ProxyConfigIdPrefix)?
Otherwise we could use some unique host property for that prefix?
Also some relative directory directive for all slotmem files
in
10 matches
Mail list logo