413 Payload Too Large for a Serverless Function with > 1MB payload

First, the Payload Too Large (413 Error) occurs because, even though the documentation states a 5MB limit, there might be a default restriction in your DigitalOcean Functions settings. Check if your function’s request body size limit is configurable. If this limit cannot be adjusted, consider uploading large files directly to Spaces from the client instead of passing them through your function.

Second, the CORS issue typically happens when your function doesn’t return the proper Access-Control-Allow-Origin headers. Since this error only appears for files over 1MB, your function might fail before sending a valid response. Ensure your function handles CORS correctly:

> response.setHeader("Access-Control-Allow-Origin", "*");
> response.setHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS");
> response.setHeader("Access-Control-Allow-Headers", "Content-Type")

If increasing the limit isn’t possible, consider switching to direct client-to-Spaces uploads using pre-signed URLs.