From: "Brian S. Wilson" <wilson96@comcast.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Questions on how to upgrade Apache
Date: Fri, 9 Apr 2021 07:59:35 -0400 [thread overview]
Message-ID: <5add3d51-b7ef-846d-6e0b-f0c294871776@comcast.net> (raw)
In-Reply-To: <CAEhDDbBdo6MnLxegfHrx=yKpmgo0DG1ARH+bQ1MeLAZyFG_BYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
>> 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
In the past, I've used the Cygwin Apache instance for local testing when
no Linux systems were available (i.e. old Windows hardware was all that
was immediately available). It gave us a good Posix like environment
and allowed us to test the effects of various configurations with
greater freedom, control, and much faster than we would otherwise have
had if we were forced to go through the corporate bureaucracy and wait
for web administrators, System Admins, purchaseing, setup,
configuration, and networking of a real or virtual system (at that time
Docker wasn't available to us either).
Windows based Apache installations are a good choice when possible, but
they are not always the same as their Linux/Posix counterparts and if
you are not concerned with the speed of execution (and you have only
Windows based hardware available); but just with testing functionality,
Cygwin offered a great way to setup a compatible environment with an
Apache server.
[-- Attachment #2: wilson96.vcf --]
[-- Type: text/x-vcard, Size: 431 bytes --]
BEGIN:VCARD
VERSION:4.0
EMAIL;PREF=1:wilson@ds.net
EMAIL:wilson96@xfinity.com
FN:Brian Wilson
ORG:The Home Depot;Dev. Tools
TITLE:Senior Systems Engineer
N:Wilson;Brian;;;
ADR:;;2250 Newmarket Pkwy SE;Marietta;GA;30067;United States of America
TEL;TYPE=home;VALUE=TEXT:+1 (678) 376-9258
TEL;TYPE=cell;VALUE=TEXT:+1 (678) 232-9357
URL;VALUE=URL:https://homedepot.com
UID:6d506c0e-6284-4e39-9c45-df7a649c804c
END:VCARD
next prev parent reply other threads:[~2021-04-09 11:59 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
2021-04-09 11:59 ` Brian S. Wilson [this message]
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=5add3d51-b7ef-846d-6e0b-f0c294871776@comcast.net \
--to=wilson96@comcast.net \
--cc=cygwin@cygwin.com \
--cc=wilson@ds.net \
/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).