CODEWITHSUNDEEP
muleapi-designraml
atiwari
atiwari

Reputation: 117

RAML mocking service POST request showing 404 Error in Mule design center

I am using mocking service feature to build and test API design for one of the POC. I am getting HTTP error code 404, when posting message from design center through mocking service.

See the attached picture as well:

The error message in the design sutdio

GET, PUT and POST request with without URI parameter are all working fine, but whenever I try to explicitly pass a specific gid or cid with the POST method it is showing the error from above.

I am attaching RAML file:

https://forums.mulesoft.com/storage/temp/6224-test.txt

I have read the documentation and have understood that we can pass any parameter value, when testing API with the mock service.

Could you please help me to find out, why the POST request with a specific gid or cid is returning an error code?

Upvotes: 1

Views: 1871

Answers (1)

Attila
Attila

Reputation: 3406

Based on the attached sceenshot you are trying to POST something to the root path of your API Mock Service.

Instead of deleting the parameters and sending the HTTP POST request to an URL like:

https://mocksvc.mulesoft.com/mocks/29b2eb87-675e-4aa2-8ae3-c5d13e99e441/

Please try to keep the URI in the correct format:

https://mocksvc.mulesoft.com/mocks/29b2eb87-675e-4aa2-8ae3-c5d13e99e441/groups/{gid}/channels/{cid}/chatthreads

In this URL you just have to replace the gid and cid parameters in the curly braces to the actual values.

Using your RAML file and a URI in the correct format, like the followine examples:

https://mocksvc.mulesoft.com/mocks/29b2eb87-675e-4aa2-8ae3-c5d13e99e441/groups/10/channels/5/chatthreads
https://mocksvc.mulesoft.com/mocks/29b2eb87-675e-4aa2-8ae3-c5d13e99e441/groups/10/teams

I am getting "204 No Content":

204 No Content

But when I remove the parameters and try to execute the HTTP POST on the wrong path, then I get "404 Not Found":

404 Not Found

Based on the screenshot you have provided; the path to the resource was not complete in your HTTP request. This could have caused the HTTP error code "404 Not Found".

Please make sure that the full path to the resource is set in the API Console. This is needed to be able to identify what resource you want to POST (create).

For details about the usage of special characters (like '-' or '$') in the names of resources; please see the raml-js-parser. This parser is being used by the API Designer.

At the moment there are still open issues related to the handling of special charachters, like '-'. Please see the related bug report: Resource name is invalid: illegal character #129 in the github repository of raml-js-parser.

I would suggest to be using no special charachters in the resource names. (even though the current RFC standards eventually do allow the usage of '$')

According to this; the resource name "$ref" seems to be causing problems in your RAML. Please consider filing a bug report for the API designer in their github repository. However the issue could be caused by the parser as well...

Upvotes: 0

Related Questions