RE: [VOTE] CMS site migration
-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 don't care one way or the other [ ] : -1 leave httpd-site as-is, because... Note: this vote is only for httpd-site, not any of the externals (eg the docs trees) that are pulled in. T-72 hours before the results are tallied. Voting rules are majority-consensus, same as for releases. Regards Rüdiger
Re: c conf 2012
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 might be interested in http://www.links.org/?p=1242 (given Hardening/exploiting modern C code bases). I think it would be great if we could get a few talks submitted about APR and HTTPD too, two projects with a long C history. I personally plan on being there if anyone wants to meet up then -Paul
Re: [VOTE] CMS site migration
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 removed, so there is no chance for confusion. Regards, Graham -- smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] CMS site migration
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 Leggett minf...@sharp.fm To: dev@httpd.apache.org Cc: d...@httpd.apache.org d...@httpd.apache.org Sent: Wednesday, May 9, 2012 6:06 AM Subject: Re: [VOTE] CMS site migration 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 removed, so there is no chance for confusion. Regards, Graham --
Re: [VOTE] CMS site migration
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 Subject: Re: [VOTE] CMS site migration T he 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 Leggett minf...@sharp.fm To: dev@httpd.apache.org Cc: d...@httpd.apache.org d...@httpd.apache.org Sent: Wednesday, May 9, 2012 6:06 AM Subject: Re: [VOTE] CMS site migration 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 removed, so there is no chance for confusion. Regards, Graham --
Re: [VOTE] CMS site migration
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 :).
Re: [VOTE] CMS site migration
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 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 :).
Re: [VOTE] CMS site migration
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
httpd-2.4.2 - bug in ProxyErrorOverride
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 module/proxy/mod_proxy_http - ap_proxy_http_process_response - ap_discard_request_body(backend-r) (modules/http/http_filters) before timing out with ProxyTimeout. ProxyErrorOverride Directive: http://httpd.apache.org/docs/current/mod/mod_proxy.html#proxyerroroverride Best regards, Zisis
Re: httpd 2.4.2 - mod_proxy id name not unique
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 mod_proxy_balancer would be nice (ap_slotmem_provider_t-create). Maybe BalancerSlotmemDir. So DefaultRuntimeDir + BalancerSlotmemDir would build up the path for the slotmem files. Best regards, Zisis - Original Message - From: Jim Jagielski j...@jagunet.com To: dev@httpd.apache.org Sent: Tuesday, May 1, 2012 8:43:46 PM Subject: Re: httpd 2.4.2 - mod_proxy id name not unique Let me look into that... iirc, it was due to us wanting to be able to persist data between restarts and using the time as part of the id prevented that. But I could be mis-remembering. On Apr 30, 2012, at 7:50 AM, Zisis Lianas wrote: hi, when mod_proxy currently is generating his id, the name of this id is not very unique. So if you have a shared config/ logs dir for more instances, the slotmem-shm files generated in DefaultRuntimeDir are the same. Bit unlucky if working with shared file systems. In httpd-2.4.2/modules/proxy/mod_proxy.c line 1146 I can see the following code: #if 0 id = ap_proxy_hashfunc(apr_psprintf(p, %pp-% APR_TIME_T_FMT, ps, apr_time_now()), PROXY_HASHFUNC_DEFAULT); #else id = ap_proxy_hashfunc(apr_psprintf(p, %pp, ps), PROXY_HASHFUNC_DEFAULT); #endif Primarily checked in with http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/proxy/mod_proxy.c?r1=1065749r2=1065748pathrev=1065749 If activating the first ap_proxy_hashfunc call, the generated names seem to be unique. Is there any reason this code is not used? Maybe we can set the timed version as default? best regards, Zisis
