By default, MetaDefender Core will always require client to upload payload data over HTTP(S) for processing, which we call it as “remote scan” with REST interface supported.
However, if the file resides on the same machine with MetaDefender Core, or resides on a local networked drive where MetaDefender Core could access and read without any authentication required, the product will support clients to specify absolute file path for processing, no need for payload uploaded in HTTP(S) body then.
“ALLOW SCAN FILES ON SERVER” option must be enabled under desired workflow rule to leverage this feature
Starting with MetaDefender Core 4.19.1, the path under above setting could accept UNC path (besides local folder path)
From client side, expecting to use filepath header under HTTP(S) file request - 18.104.22.168. Process a file