linking to http://stackoverflow.com/questions/6491419/apache-ignoring-php-headers-when-sending-a-304 here so new server implementers are warned about that.
FYI: Apparently it’s fixed in upstream, but not in a release version yet.
oh, that’s good news!
Only 6 years later, it’s actually finally fixed in trunk AFAICS: https://bz.apache.org/bugzilla/show_bug.cgi?id=61820
So, hopefully Apache 2.5 will finally be fixed for RS servers.
Backported to v2.4.47
I just attempted to set up
php-remote-storage with Apache on a fresh Ubuntu 20.04 VM. In the process, I verified (to no surprise) that CORS headers are indeed missing for 304 responses.
Unfortunately, there’s no backport for the official
apache2 apt package for newer Apache versions. However, there is a decent PPA, which contains the latest Apache stable release. But that’s actually still
2.4.46, so I’ll wait until
2.4.47 lands there and try again.
I have notes for an install from scratch now, incl. setting up a Let’s Encrypt certificate, and it’ll be really simple for anyone using Apache on Ubuntu, as soon as there’s a package available for the fix.
Hi! I’ve also recently tried apache on a debian 10 VM with php-remote-storage and CORS headers are always missing. I’ve used nginx instead of apache and it works after some trials on configs, but it seems php-remote-storage doesn’t works as intended… I’ve bugs on PUT for update data with an error “document already exists” that doesn’t appears when I use 5apps remote storage server… Is there a stable server implementation somewhere ? (armadietto doesn’t seems ready too according to my last attempts).
php-remote-storage should be rather stable. Could you open an issue over on its GitHub repo, with details of the situation?
It’s finally here:
Apache HTTP Server 2.4.49 Released
September 15, 2021
The Apache Software Foundation and the Apache HTTP Server Project
are pleased to announce the release of version 2.4.49 of the Apache
HTTP Server (“Apache”). This version of Apache is our latest GA
release of the new generation 2.4.x branch of Apache HTTPD and
represents fifteen years of innovation by the project, and is
recommended over all previous releases. This release of Apache is
a security, feature and bug fix release.
We consider this release to be the best version of Apache available, and
encourage users of all prior versions to upgrade.
Apache HTTP Server 2.4.49 is available for download from:
Apache 2.4 offers numerous enhancements, improvements, and performance
boosts over the 2.2 codebase. For an overview of new features
introduced since 2.4 please see:
Please see the CHANGES_2.4 file, linked from the download page, for a
full list of changes. A condensed list, CHANGES_2.4.49 includes only
those changes introduced since the prior 2.4 release. A summary of all
of the security vulnerabilities addressed in this and earlier releases
This release requires the Apache Portable Runtime (APR), minimum
version 1.5.x, and APR-Util, minimum version 1.5.x. Some features may
require the 1.6.x version of both APR and APR-Util. The APR libraries
must be upgraded for all features of httpd to operate correctly.
This release builds on and extends the Apache 2.2 API. Modules written
for Apache 2.2 will need to be recompiled in order to run with Apache
2.4, and require minimal or no source code changes.
When upgrading or installing this version of Apache, please bear in mind
that if you intend to use Apache with one of the threaded MPMs (other
than the Prefork MPM), you must ensure that any modules you will be
using (and the libraries they depend on) are thread-safe.
Please note the 2.2.x branch has now passed the end of life at the Apache
HTTP Server project and no further activity will occur including security
patches. Users must promptly complete their transitions to this 2.4.x
release of httpd to benefit from further bug fixes or new features.
… also available on Ubuntu today, via this PPA: