files.js self._handleUploadFail, so upload is done via browser and from a slicer or other client.
I ask the user if there is a reverse-proxy between his browser and the the octoprint server, but my assumption is that is a direct connection. waiting for feedback.
The file upload is done (blue progress bar increasing, with text uploading), after that the text is switching to save (or saving) with color-animation. During that process the preprocessing hooks scans each single line, with several expressions:
I already optimised the process performance up to 40-50%, I just evaluate only comment-lines and skip any other line. Thats the reason why 50MB files now works for him, but 100MB is still not working.
In my environment I didn't receive a gateway timeout, instead after 15 minutes a popup appears with the message "server is offline. automatic reload not possible". A manual reload (Strg+F5) is not possible "spinning wheel of death"...because file is still processing.
The preprocessing took round about 28 minutes (enabled logging per line, Raspberry Pi-3B, 50MB Cura g-code)
Any other ideas...my lates idea is to create a separate thread for analysing, if the file-size reach a defined threshold.