From: Csaba Raduly <rcsaba@gmail.com>
To: Andy Romens <Romens.Andy@hotmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Questions on how to upgrade Apache
Date: Fri, 9 Apr 2021 11:08:28 +0200 [thread overview]
Message-ID: <CAEhDDbBdo6MnLxegfHrx=yKpmgo0DG1ARH+bQ1MeLAZyFG_BYw@mail.gmail.com> (raw)
In-Reply-To: <CH0PR14MB4930303E2223FEE2607CFB23FB769@CH0PR14MB4930.namprd14.prod.outlook.com>
Hi Andy,
On Tue, 6 Apr 2021 at 22:35, Andy Romens via Cygwin wrote:
>
> Hi Cygwin,
>
> I got a question for you all. Our cyber security team is yelling at us to update Apache from 2.4.39 to 2.4.46.
If that website is customer-facing, your cyber security team and your
ops team should be yelling at you for running Apache on Cygwin.
If you want to run Apache on Windows, you would be much better served
by native Apache builds (as others have suggested) -
http://httpd.apache.org/docs/current/platform/windows.html#down
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
next prev parent reply other threads:[~2021-04-09 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 20:34 Andy Romens
2021-04-06 20:37 ` Andy Romens
2021-04-08 5:30 ` Andrey Repin
2021-04-09 0:26 ` Brian S. Wilson
2021-04-08 13:22 ` Andy Romens
2021-04-08 14:33 ` Stephen John Smoogen
2021-04-08 15:49 ` Andy Romens
2021-04-08 15:57 ` Eliot Moss
2021-04-08 16:37 ` René Berber
2021-04-08 18:33 ` Glenn Strauss
2021-04-08 19:53 ` bzs
2021-04-09 6:23 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-04-09 9:08 ` Csaba Raduly [this message]
2021-04-09 11:59 ` Brian S. Wilson
2021-04-09 14:46 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEhDDbBdo6MnLxegfHrx=yKpmgo0DG1ARH+bQ1MeLAZyFG_BYw@mail.gmail.com' \
--to=rcsaba@gmail.com \
--cc=Romens.Andy@hotmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).