MapGuide RFC 165 - Upgrade Apache, Tomcat and PHP
This page contains a change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.
|RFC Template Version||(1.0)|
|Submission Date||24 Jan 2018|
|Last Modified||1 Mar 2018|
|Assigned PSC guide(s)||(when determined)|
|Voting History||(vote date)|
This RFC proposes to upgrade Apache, Tomcat and PHP to the latest versions:
- Apache: 2.4.29
- PHP: 5.6.33
- Tomcat: 7.0.85
From a security standpoint, our public-facing web tier components should be regularly kept up to date. New versions of Apache, Tomcat and PHP have been released since the previous RFC
Upgrade Apache to 2.4.29. Windows binaries will be sourced from Apache Lounge
Upgrade PHP to 5.6.33. Windows binaries will be sourced from windows.php.net. We are staying on the 5.6.x series because it is not possible to upgrade to the current PHP 7.x series as our copy of SWIG cannot generate PHP7-compatible language bindings for the MapGuide API.
Upgrade Tomcat to 7.0.85. We are staying on the 7.x series so that our Java installation requirements do not have to change for this release of MapGuide.
As the 3.1 release has been using the same series of Apache/PHP/Tomcat, the 3.1 branch will also be recipients of this component upgrade.
Due to the adoption of MapGuideRfc166, we will only keep 64-bit Apache/PHP/Tomcat binary artifacts for the windows installer project for trunk (that the 3.3 release will branch from when ready), but retain 32 and 64-bit copies for the windows installer on the 3.1 branch.
None. These new component updates are all bug fix releases.
Build and run on Windows and Linux. Ensure that components using PHP or Java function as before:
- The PHP AJAX Viewer
- The Java AJAX Viewer
- The PHP backend for Fusion trunk
- The MapGuide Site Administrator
- The Feature Source schema report.
Verify all tests pass with the existing MapGuide API PHP test runner.
Funding / Resources