httpd.conf Changes After Upgrading FileCloud on Windows (23.253.2 → 23.253.3)

Original Question or Issue:

After upgrading FileCloud Server from 23.253.2.31793 to 23.253.3.31801 on Windows Server, the customer observed larger-than-expected changes in the httpd.conf file and wanted confirmation that these changes were intentional before proceeding, due to a high-severity OpenSSL vulnerability.

Environment:

• Product - FileCloud Server
• Version - 23.253
• Platform - Windows, Linux, MacOS

Steps to Reproduce:

1. Install FileCloud Server version 23.253.2.31793 on Windows Server.

2. Upgrade to version 23.253.3.31801.

3. Compare C:\xampp\apache\conf\httpd.conf before and after upgrade.

4. Observe significant configuration differences.

Error or Log Message:

No specific error message. Concern raised due to noticeable configuration changes in httpd.conf.

Defect or Enhancement Number:

No JIRA assigned

Cause:

Version 23.253.3 includes Apache and OpenSSL updates along with additional security hardening changes. During the upgrade process, configuration files such as httpd.conf may be replaced with updated versions. Custom modifications are not automatically merged into the new configuration file.

Resolution or Workaround:

• Confirmed that the changes in httpd.conf are intentional.

• Advised the customer to:

  • Back up the original configuration file.

  • Compare old and new versions.

  • Manually reapply only necessary custom settings.

  • Avoid replacing the entire updated file with the old one.

Customer confirmed their only customization was disabling port 80.
Upgrade was reattempted, customization reapplied, and completed successfully.

Notes:

• Upgrading to 23.253.3 is strongly recommended due to the high-severity OpenSSL vulnerability addressed in this release.

• Administrators should always review and manually merge custom Apache or PHP configurations after upgrades.