[users@httpd] Apache Version for OpenSSL 1.1.0
Team, Any idea when will Apache is going to release latest version which will OpenSSL 1.1.0?. Thanks Sundar
Re: [users@httpd] Showing exact filesize in bytes instead of shortform in directory listing
On 03/10/16 19:35, Rich Bowen wrote: Or use rsync WebDAV would be more on-topic. -- With Best Regards, Marat Khalili - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Showing exact filesize in bytes instead of shortform in directory listing
On 09/30/2016 09:55 AM, Christopher Schultz wrote: >> > Background: I want to mirror the directory with lftp, and lftp can >> > not read the given filesize correctly out of the index. So lftp has >> > to make HEAD requests to get the file size for each file. The >> > additional HEAD requests would be not necessary if the index >> > returns the exact file size. >> > > It sounds like this is a good candidate for a web service which > returns exactly the information you need and no more. For example, if > you were to return the list of files and their file sizes as a CSV or > something simpler than an HTML document, you would be able to do it > even more easily. Or use rsync -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon signature.asc Description: OpenPGP digital signature
RE: [users@httpd] TLS Proxy client certificates per virtualhost
We do extensive multi-tenant hosting inside a single Apache instance (config) and so different virtualhosts want differential, virtualhost-specific secured proxy connections, client certificates, yes. We are probably pushing the sensible limits of what you should be doing inside a single configuration/instance though. > -Original Message- > From: Marat Khalili [mailto:m...@rqc.ru] > Sent: 30 September 2016 17:33 > To: users@httpd.apache.org > Subject: Re: [users@httpd] TLS Proxy client certificates per virtualhost > > Do you mean proxy _client_ certificates? That is, certificates for > identifying your proxy to upstream server(s)? Looks like there's indeed > no option to make them virtual-host dependent. I wonder why do you need > it. > > Local server (proxy or not) certificates can be made virtual-host > dependent using SSLCertificateFile etc. Likewise, remote server CA > certificates can be made virtual-host dependent using > SSLProxyCACertificateFile etc. > > -- > > With Best Regards, > Marat Khalili > > On 30/09/16 17:42, Mark Blackman wrote: > > Hi, > > > > What kind of options do I have if I want to use different SSL proxy > certificates for different virtual hosts? > > > > SSLProxyMachineCertificateFile is close, but only has server scope. What's > the equivalent for virtualhost context? > > > > I have a feeling I have zero options, but would like to confirm that here, > please. If so, how much work would it take to provide that? > > > > Regards, > > Mark > > > > > > > > --- > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) please > notify the sender immediately and delete this e-mail. Any unauthorized > copying, disclosure or distribution of the material in this e-mail is strictly > forbidden. > > > > Please refer to https://www.db.com/disclosures for additional EU > corporate and regulatory disclosures and to > http://www.db.com/unitedkingdom/content/privacy.htm for information > about privacy. > > > > - > > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > > For additional commands, e-mail: users-h...@httpd.apache.org > > > > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
RE: [users@httpd] TLS Proxy client certificates per virtualhost
Great, thanks. Although I really need it for Apache 2.2 as well :) I will see if we can find some time for it. > -Original Message- > From: Rainer Jung [mailto:rainer.j...@kippdata.de] > Sent: 30 September 2016 18:12 > To: users@httpd.apache.org > Subject: Re: [users@httpd] TLS Proxy client certificates per virtualhost > > Hi Mark, > > in trunk sinve a few months we've got the feature, that any SSLProxy* > directive can be used in vhosts but more important per block. > The feature is proposed for addition to 2.4.x. Currently two more > reviewers are needed. The proposed patch is available at > > http://home.apache.org/~ylavic/patches/httpd-2.4.x- > r1740928_and_co.patch > > If you can try and test it with a custom build of 2.4.x your feedback > will be very welcome and might speed up the review process. > > Some background discussion is available at: > > https://marc.info/?t=14605441672&r=1&w=2 > > Regards, > > Rainer > > Am 30.09.2016 um 16:42 schrieb Mark Blackman: > > Hi, > > > > What kind of options do I have if I want to use different SSL proxy > certificates for different virtual hosts? > > > > SSLProxyMachineCertificateFile is close, but only has server scope. What's > the equivalent for virtualhost context? > > > > I have a feeling I have zero options, but would like to confirm that here, > please. If so, how much work would it take to provide that? > > > > Regards, > > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
