Added the directive at the place you suggested:
Require all denied
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
Restarted only apache, and it didn’t work. Restarted all services. Didn’t work. Rebooted the instance, and still, didn’t work.
Apache still waits for the whole file/upload to finish, and then return
On my local machine (using XAMPP), however, I get
413 Request Entity Too Large and the following when using the same setup (configurations and single.php):
Request Entity Too Large
The requested resource does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
Apache/2.4.47 (Win64) OpenSSL/1.1.1k PHP/8.0.6 Server at localhost Port 80
I don’t mean any disrespect, but are we going to continue this single check/test daily? There’s no reason for me to do these tests (about
LimitRequestBody). I’m using a fresh instance/LAMP to eliminate any user errors. While I may have done some mistakes with the php configuration (wrong instance report, etc.) I don’t think it’s the case with this one.
I suppose you (the bitnami team) can easily verify this issue by creating an instance on AWS Lightsail yourselves. If there’s an issue with the LAMP stack, this doesn’t just concern me (a single user). So I can’t make sense of the situation we’re in right now.
Also, in light of this issue, Modify The PHP File Upload Limit page might need to be updated. Following the suggestions in the page obviously doesn’t work.
If you guys can’t/won’t test an instance on AWS Lightsail yourselves for whatever reason, I can provide access to the instance in question if it’s going to speed up the process.