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

REST delete request fails on server redirection

SA-43852

Summary



The HTTP response code of 301 indicates a server redirection which is not supported for HTTP connectors using the Delete method. The body of the service's response, which is set up for mapping in the Connector rule, is empty for this service call.

A REST delete request fails with errors in logs.



Error Messages

The property pyTempDataPage.response_POST.employee was of mode String while com.pegarules.data.internal.ClipboardPropertyStrMinFeatureImpl.getPageValue(int) was expecting Page List mode. Details: (none)
 

Steps to Reproduce



Send a REST delete request.


Root Cause



When capturing the traffic, the request is made to /path/to/resource , while the redirect is to /path/to/resource (note the trailing forward slash). The delete request fails as Pega does not support redirects in REST.

Resolution



Perform the following local-change: 

Change the REST delete request to /path/to/resource/ (include the trailing forward slash).


 

Published October 11, 2017 - 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