Product and version: FileMaker Server 188.8.131.526
OS and version: Windows Server 2016, Version 1607, Build 14393.2273
Browser and version (for WebDirect only): Client browsers vary. Typically iPhone Safari or Android Chrome.
Hardware: Virtual machine. AWS Windows AMI running on an m5.large instance.
Description: Files uploaded via WebDirect using the Insert File script step appear to be staged automatically by FileMaker Server within the following directory:
C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\Documents\Import
Within at least one deployment of FileMaker Server 184.108.40.2066, this directory never gets cleared. Thus, if you host a WebDirect app that frequently processes large file uploads, this directory can quickly consume most of the available space on C.
As far as I know, the behavior of this directory is not officially documented. This FileMaker Community discussion thread suggests the directory should be cleaned up automatically following the completion of an upload, the end of a WebDirect user's session, a restart of the Web Publishing Engine, or a reboot of the server: optimizing insert file ("insert to container") via WebDirect?
How to replicate:
- Upload a file to a container field using the Insert File script step in WebDirect.
- Confirm that the uploaded file is in the Import directory on C.
- Observe that the contents of the Import directory do not change following the completion of the upload, the end of your WebDirect session, a restart of the Web Publishing Engine, or a reboot of the server.
Workaround (if any): Log in to the server and manually delete the contents of the Import directory.