ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CEM Unable to Handle "Content-Type: multipart/form-data" for the POST

book

Article ID: 132579

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE

Issue/Introduction



Why can't CEM handle "Content-Type: multipart/form-data" for the POST?

Environment

Release:
Component: APMCM

Resolution

This is currently a product limitation.
Requests with "Content-Type: multipart/form-data" are normally in HTTP for uploading files (for example, that's how CEM software is installed). It is the same mechanism used for email attachments, and the sub-parts are sometimes called attachments in HTTP.
With this content type, each attachment has its own headers. Usually each attachment has a "Content-Type:" and "Content-Disposition:" header.
CEM could be extended to handle this kind of data by adding a new parameter type called "attachment," so that you could use the value of the "name" attribute in the Content-Disposition header as the parameter name, and the body of the attachment as the parameter value.

Workaround:
Change the ENCTYPE attribute in their HTML forms from "multipart/form-data" to "application/x-www-form-urlencoded." Then the form submissions will generate the kind of POST parameters that CEM already recognizes.