BlucaScan Documentation

File Transfer Configuration

Configure how BlucaScan transfers clean files to your destination server. Set up transfer protocols, endpoints, and security settings.

Basic configuration for file transfer settings

{
  "fileTransfer": {
    "transferProtocol": "HTTP",
    "transferUrl": null
  }
}

Transfer Protocol

Currently supports HTTP protocol for file transfers

HTTP

Transfer URL

Destination endpoint where clean files will be sent

Configurable

Transfer Process

File Scanning

File is scanned for malicious content

Clean Verification

System confirms file is clean

HTTP Transfer

File sent to configured endpoint

Confirmation

Transfer status reported back

Transfer Statuses

SUCCEEDED

File successfully transferred to destination

ASYNC_ONGOING

Transfer in progress (background processing)

SKIPPED

Transfer intentionally not attempted

FAILED

Transfer failed due to error

Configuration Examples

Common file transfer configuration scenarios

Basic HTTP Transfer

{
  "fileTransfer": {
    "transferProtocol": "HTTP",
    "transferUrl": "https://your-server.com/api/files/upload"
  }
}

Transfer Disabled

{
  "fileTransfer": {
    "transferProtocol": "HTTP",
    "transferUrl": null
  }
}

When transferUrl is null, files are scanned but not transferred

Security Note: Only files that pass all security scans are transferred. Malicious files are never sent to your destination server, regardless of configuration.

Best Practices

Recommendations for secure file transfer setup

Use HTTPS Endpoints

Always use secure HTTPS URLs for file transfer endpoints

Implement Authentication

Secure your transfer endpoint with proper authentication

Monitor Transfer Status

Use webhooks to track transfer completion and failures

Handle Large Files

Configure appropriate timeouts for large file transfers