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.
Unable to log ${request.mainpart} when a custom contentType is being used
Article ID: 8081
Updated On:
Products
STARTER PACK-7
CA Rapid App Security
CA API Gateway
Issue/Introduction
Several of context variables may not return a value if a custom context type is being used
${request.mainpart}
${request.parts[0]
${request.parts.0.body}
${request.parts.0.mainpart}
${request.parts[1]
${request.parts.1.body}
${request.parts.1.mainpart}
Environment
Release:
Component: APIGTW
Component: APIGTW
Resolution
Add the cluster wide property contentType.otherTextualTypes with the value of custom context type being used.
Example: application/vnd.lotsys.motors.event.request-1+json
Feedback
Yes
No
Powered by
