Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    11
  • Views views
    66
  • Users 0 members are here
Related
Options

How to handle custom request which is showing 400 Bad request while replay

Ezhilarasi C

I am trying to send the below request as shown in the screenshot. Though i have give the required headers, content type etc. as required by the request while replay the request body is send in unknown language where as the same is recorded properly. Kindly help me to understand what is missing here 

 

  • Suggested Answer

    0  

    , You do show the headers for the correct message, but the Request Body for the failed message. That is hard to compare.
    You also hided the body content of your code.


    Because ContentEncoding is gzip, you might just see the weird characters. You might comment out the source line with "ContentEncoding=gzip" and see what you get.

    Error 400 means a Bad Request, so the payload is not expected by the server. Your payload might contain some data that needs to be changed (Correlated) from run to run.

    How to ask questions

    Reward contributions via likes or 'verified answers'

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.