Skip to Main Content
Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Workspace K2
Categories SmartForms
Created by Johan Liebenberg
Created on Nov 17, 2026

Always set Content-Type Header on file uploads from the File Attachment control

When a file is uploaded through the File Attachment control on a SmartForm, the POST to /Utilities/FileHandler.ashx doesn’t always include a Content-Type header. We see this consistently with Outlook .msg files, and it probably affects any file type the browser can’t map to a MIME type, since the browser then reports an empty type and the request goes out without the header.

This matters when K2 sits behind a web application firewall or reverse proxy. We’re testing Azure Front Door in front of our K2 server. Front Door can’t inspect a request body without a Content-Type, so it blocks the upload. Other WAFs and API gateways often behave similarly.

Requested change: set the Content-Type header on every upload request. Use the file’s MIME type where the browser knows it, and fall back to application/octet-stream where it doesn’t.

Steps to reproduce:

  1. Open a SmartForm that has a File Attachment control.

  2. Press F12, go to the Network tab and start recording.

  3. Upload a .msg file (an email saved from Outlook).

  4. Find the POST to /Utilities/FileHandler.ashx?fn=<filename>.msg. The request has the file as its body and no Content-Type header.

Observed request sequence:

  1. The form loads (SharedResources.ashx, UserResources.ashx, then several AjaxCall.ashx calls).

  2. The upload: POST to FileHandler.ashx with the file as the body and no Content-Type.

  3. About 3 to 5 seconds later, there’s a single AjaxCall.ashx call, which looks like the SmartObject saving the attachment.

Impact: you can’t reliably put K2 behind Azure Front Door or a similar WAF without adding exclusions for FileHandler.ashx, and that weakens the protection those services exist to provide.

  • Attach files