Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

InvokeAxis2 with custom security header error



Seeing error with InvokeAxis2 after adding custom code in security header

Error Messages

HTTP :unsupported content-encoding of ', ' found

Steps to Reproduce

1. OOTB 7.1.7 Invoke Axis 2 was taken as a reference and did a Save-As to application ruleset.
2. Added the two steps to add custom security header with Java.
3. Extended configuration added to WS Security profile to support custom header.
4. Note error.

Root Cause

The service call was including certificate that was not matching the service. The handling of the response from the service correctly identified that the response header was malformed.


The certificate was corrected and the issue was resolved.

Published April 12, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us