Getting 404 response for CONNECT-REST Calls
Getting 404 response to Connect-REST calls and API team has confirmed that nothing has been registered at their end.
For debugging purpose ,REST class has been set to debug mode , we see request is forming correct but no clue for failure. it's occuring intermittently . How do we ensure that connect call has been sent from Pega ? I
appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - Mapping response parameters to clipboard
2019-07-23 07:50:27,748 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) INFO appl.Org.com|10.32.24.32|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - Starting remote service invocation...
2019-07-23 07:50:27,754 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) INFO appl.Org.com|10.32.24.32|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - HTTP Request: GET https://api.org:123/RESTv3/api/v3.0/Test/Person/XXXX-XXXX/Volume
2019-07-23 07:50:27,754 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) INFO appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - Adding outbound header values to HTTP request
2019-07-23 07:50:27,754 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) DEBUG appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - Setting header "Authorization" to value ""
2019-07-23 07:50:27,754 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) DEBUG appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - Avoiding setting request body as HTTP method is GET
2019-07-23 07:50:27,754 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) DEBUG appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX -
------------------HTTP REQUEST CONTENTS------------------GET /RESTv3/api/v3.0/Test/Person/XXXX-XXXX/Volume HTTP/1.1
Request Headers: {}
Request Message Data: N/A (this is a GET request)
----------------END HTTP REQUEST CONTENTS----------------
2019-07-23 07:50:27,800 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) INFO appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - HTTP Status code: 404 Not Found
2019-07-23 07:50:27,800 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) DEBUG appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX -
------------------HTTP RESPONSE CONTENTS------------------
Response Headers:
Cache-Control: must-revalidate,no-cache,no-store
Content-Length: 269
Content-Type: text/html;charset=ISO-8859-1
Response Message Data: 269 bytes received
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 404 Not Found</title>
</head>
<body><div style="font-family:Arial,Helvetica,sans-serif;"><h2>HTTP ERROR 404</h2>
Reason:
<pre> Not Found</pre></div>
</body>
</html>
----------------END HTTP RESPONSE CONTENTS----------------
2019-07-23 07:50:27,800 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) DEBUG appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - Reading inbound header values from HTTP response
2019-07-23 07:50:27,800 [2.10.12-443-exec-113] [TABTHREAD0] [ ] [ APP:01.01.01] ( connect.rest.RESTConnector) INFO appl.Org.com|127.0.0.1|Rule-Connect-REST.XXXXXXXX XXXX-XXXX - Reading HTTP response message data
***Edited by Moderator Marissa to update platform capability tags****
The endpoint generated this response. The API endpoint service team may not be seeing the request, but the server they're on must be.
The easiest way to debug this is to confirm the request leaves Pega and capture it fully to provide to endpoint team. I use TCPMon. Change your rule in Pega to hit the host and port that you have TCPMon listening on ... and have TCPMon forward the request on.
https://TCPMon-server:nnn/RESTv3/api/v3.0/Test/Person/XXXX-XXXX/Volume