Question
Pegasystems Inc.
JP
Last activity: 20 Jun 2019 21:21 EDT
Pega Platform can't handle REST endpoint URL that ends with slash
Hi,
There is an external system whose endpoint URL ends with slash:
http://myserver.com/winactor_service/services/winactorjob/restapi/token/
As far as I know, most of REST URL does not have slash at the end of URL, but there seem to be some out there. If I make a REST request without slash, it gets an HTTP status code 404 error (Not found) and I need to do this with slash.
Now, I want to run a REST Connector wizard. However, when I include a slash as below, wizard won't let me go next as it validates.
In such case, is it Pega Platform wizard defect? Or, is this external system's URL not well designed (not RESTful)?
Thanks,
Accepted Solution
Pegasystems Inc.
US
Pegasystems Inc.
JP
Thanks Kevin for your comment, and I agree with your opinion. FYI, here is the workaround:
1. Proceed without slash in the wizard (step 1 ~ step 2).
2. In step 3 screen, click "+ Add a REST response" to show below popup.
3. With popup displayed, open a clipboard and search the URL to locate it in pyWorkPage.
4. Manually edit the value from clipboard to add slash at the end.
5. Run button should work and you can complete the wizard without any error.
Thanks,
Normally it is the best practice not to use ending slash and it adds no value (see this link: https://restfulapi.net/resource-naming/). Now that is not enforced, some tools do accept ending slash (e.g., Postman). I would not this is a defect, but more as designed. At best, it would be a 'nice to have' enhancement.