topic Internal: Unexpected error Cannot send a content-body with this verb-type in Product Forum

Internal: Unexpected error Cannot send a content-body with this verb-type

MarcoD_Incà — Thu, 16 Jun 2022 08:04:39 GMT

I'm having some trouble getting a GET Action with body to work in BluePrism (using web api service).

It seems that when I try to include an Action that sends a GET with body when I reach that stage this error gets thrown:

Internal : Unexpected error Cannot send a content-body with this verb-type.

What I've tried:

Using a different verb-type / passing parameters in the query instead of the body, unfortunately i don't have control over the endpoint i'm trying to reach so this didnt work as it only accepts a GET containing data in the body
Using BluePrism HTTP Utility to send the call, this has the same problem as the Web API Service
Compiling the body via code instead of using a template

I haven't been able to find anyone that made it work in BluePrism and there doesn't seem to be much documentation on this issue so any help would be appreciated.

Thanks!

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

shashank.kumar280 — Thu, 16 Jun 2022 08:40:52 GMT

Hi Marco,

Typically HTTP POST requests have body in the request. Which application endpoint is it? Do you have any documentation for what is the expected format of the HTTP Request?

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

MarcoD_Incà — Thu, 16 Jun 2022 08:49:40 GMT

Hi Shashank,
the endpoint isnt a part of any public-facing service, this is the relevant snippet from the documentation:

The HTTP Request should then be a GET with the Content-Type: application/json header and a json object as the body.

It's unclear why the endpoint was set up this way, but it seems we need to make it work with this format.

Thank you for the help

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

shashank.kumar280 — Thu, 16 Jun 2022 10:02:04 GMT

I see the documentation. It should have been a POST request for /api/bot/getFile. By the way are you able to call /api/bot/getRerun and get the filePath?

What response do you get if you do POST /api/bot/getFile

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

MarcoD_Incà — Thu, 16 Jun 2022 10:09:10 GMT

Yes, I'm able (using Postman) to call the endpoint using the way described in the documentation.

If I try to call the endpoint using POST I recieve this response:

{
    "timestamp": "2022-06-16T10:07:52.452+00:00",
    "status": 405,
    "error": "Method Not Allowed",
    "path": "/api/bot/getRerun"
}

My question is: is there any way to configure BluePrism in order to make GET calls with a body possible?

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

shashank.kumar280 — Thu, 16 Jun 2022 10:23:41 GMT

I was looking at this documentation on Mozilla if there is a restriction to send payload in HTTP. https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/GET ; It doesnt seem that there is a restriction there.

What response do you get for below-

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

MarcoD_Incà — Thu, 16 Jun 2022 10:49:23 GMT

I get the same error:

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

ewilson — Fri, 24 Jun 2022 00:37:44 GMT

The error you're running into is not an error being raised by Blue Prism, but by the underlying .NET Framework. This might boil down to having to invoke curl from the command line or using a TcpClient class which is lower level than the WebRequest class used in the Utility - HTTP VBO.

Cheers,
Eric

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

Tejaskumar_Darji — Mon, 12 Jun 2023 14:07:57 GMT

Hello Marco D'Incà

Were you able to resolve this? We are running into the same and tried all possible scenarios with the API call.

Re: Internal: Unexpected error Cannot send a content-body with this verb-type

Tejaskumar_Darji — Wed, 14 Jun 2023 08:31:19 GMT

Update - Setting Force Pre Authorization input para to True resolved this error for us. FYI