[Package Request]: Apache Httpd

[hwhsu1231]

Package Requested

• [X] I would like someone else to build the manifest.
• [ ] I would like help so I can submit the manifest.
• [X] I have performed a search and couldn't find this package.
• [x] I have checked that the installer for this package is not contained in a .zip file
• [ ] I think there is a new version available and I have provided the URL.

Please provide the following information

Publisher: Apache Haus, Apache Lounge Publisher Url: https://httpd.apache.org/docs/current/platform/windows.html Package Name: Apache Httpd Description: Apache HTTP Server on Microsoft Windows Package Version: 2.4.54 Installer URL:

• Apache Haus: https://www.apachehaus.com/cgi-bin/download.plx
• Apache Lounge: https://www.apachelounge.com/download/

----- Updated 2023/03/04 -----

Publisher: https://archive.apache.org Publisher Url: https://archive.apache.org/dist/httpd/binaries/win32/ Package Name: Apache Httpd Description: Apache HTTP Server on Microsoft Windows Package Version: ~2.2.25 Installer URL:

• no_ssl version:

  • apache_2.0.35-win32-x86-no_ssl.msi
  • apache_2.0.36-win32-x86-no_ssl.msi
  • apache_2.0.39-win32-x86-no_ssl.msi
  • apache_2.0.40-win32-x86-no_ssl.msi
  • apache_2.0.42-win32-x86-no_ssl.msi
  • apache_2.0.43-win32-x86-no_ssl.msi
  • apache_2.0.44-win32-x86-no_ssl.msi
  • apache_2.0.45-win32-x86-no_ssl.msi
  • ...
  • httpd-2.0.64-win32-x86-no_ssl.msi
  • httpd-2.0.65-win32-x86-no_ssl.msi
  • httpd-2.2.15-win32-x86-no_ssl.msi
  • httpd-2.2.16-win32-x86-no_ssl.msi
  • httpd-2.2.17-win32-x86-no_ssl.msi
  • ...
  • httpd-2.2.25-win32-x86-no_ssl.msi

Current Package Identifier (for new versions):

[mdanish-kh]

@msftbot .zip

[mdanish-kh]

@hwhsu1231

Apache Haus: https://www.apachehaus.com/cgi-bin/download.plx Apache Lounge: https://www.apachelounge.com/download/

These are blocked by Zipped-Binary issue

Regarding the MSI Installers: I was going to add the two variants, the NoSSL and the OpenSSL ones in separate PackageIdentifiers as Apache.HttpServer.NoSSL and Apache.HttpServer.OpenSSL

The issue I see with this approach is that they have identical Registry values for DisplayName, Publisher, ProductCode etc. WinGet won't be able to distinguish between the two until Release Channels support is completed. In the current implementation, as the Registry values are same, users would be prompted for an upgrade to NoSSL version from an OpenSSL version and vice-versa

So, I guess the best option here would be to have the SSL installer in Apache.HttpServer in WinGet?