Support Article

Calling Pega ping service with HTTP HEAD causes HTTP 500



Pega ping service is called, to test if the system is available, with an HTTP HEAD request. An HTTP 500 response is received in doing so.

Error Messages

HTTP 500

Steps to Reproduce

Send HTTP HEAD to the Pega ping service.

Root Cause

The issue was caused by an incorrect configuration.


Refer to the following PDN article:

Note: This does contain a message body where a HEAD request does not. The message body is, as indicated, JSON that contains:
{ "duration":"<time in milliseconds>" }

Published August 24, 2016 - Updated September 1, 2016

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.