Kyudos wrote: ↑
Tue Aug 27, 2019 9:02 pm
It all points to a problem with the file system on the server, I'll just have to continue trying to debug the problem from that end.
To me it feels like the evidence isn't exactly pointing to "the file system." All we know for sure is that the web server appears to have not made a response to the otherwise successful POST containing file upload data.
Having a PHP execution failure -- or even encountering some kind of PHP limit -- would certainly explain "not getting the response we expected
". But those conditions would typically still generate some kind of response; like an HTTP 500 failure response.
But we're not even seeing a failure response in this case. Its more like "the web server never received the POST at all" (which seems unlikely, given that the LAN trace shows the TCP stack has acknowledged receipt of the POST data that was sent), or "the web server is still working on creating the response" (but after 600 seconds still hadn't been able to complete it).
Still, its worth checking your web server error log and the PHP error log (if that's not part of the web server error log) just to make sure there isn't a failure being reported which has aborted the attempt to return a response.
The idea just came to mind that possibly the web server wasn't allowing the "application/json"
-type response to be returned in the file upload case; as compared to the "text/html"
responses generated for most pages. But I just now tested the "Delete cookies" link on your site, and the "application/json"
response involved there came through successfully.
If this issue were happening on my site, the next step would be to put some debug code in the posting.php module, in order to prove whether the uploaded file POST actually makes it that far (and the response becomes botched somewhere after that). Versus whether posting.php never gets invoked (suggesting the upload file POST was eaten or dropped somewhere before PHP or phpBB ever received it).
Because that would be the start of a "divide and conquer" approach to confirm whether you're looking for something within the web server configuration (because posting.php never even had a chance to see the file upload submission), versus whether you're looking for something within the posting.php execution itself which has failed to create a response.