UCCX: Make Rest Call return 400 Bad request

[Mario C. G.]

Hi,

I have a problem when I try the step Make Rest Call, I received 400 bad request error.

But If I try the URL from any browser or PostMan the URL working fine, only with UCCX fail.

Can you help me

Regards

[Sean Lynch]

Google:

A 400 Bad Request Error indicates that the server (remote computer) is unable (or refuses) to process the request sent by the client (web browser), due to an issue that is perceived by the server to be a client problem. ... If an expected custom HTTP header is missing or invalid, a 400 Bad Request Error is a likely result.

Review your UCCX MIVR tracelogs and post the details of why the request was rejected.

-Sean

[Mario C. G.]

Hi Sean,

Thank you for your help.  I attach the part log.

147614794: Oct 16 13:05:04.813 CDT %MIVR-STEP_REST-7-UNK:Task: 48000264972 The parameters for the REST call are URL=http://xxxxxx/xxxNetNxServices/serviceRest/usuarios/validarUsuario?clave=123456, USERNAME= and CONTENT-TYPE=application/json

147614798: Oct 16 13:05:04.819 CDT %MIVR-EXPR_MGR-7-UNK:modifying identifier 'SDetalles' (5) = GET http://xxxxxxx/xxxNetNxServices/serviceRest/usuarios/validarUsuario?clave=123456 returned a response status of 400 Bad Request

147614799: Oct 16 13:05:04.819 CDT %MIVR-STEP_REST-7-UNK:Task: 48000264972 Response from the rest call is: Bad request.

Regards

[Sean Lynch]

After looking at the data provided, I don't see anything that stands-out as wrong.  And it's kind of hard to see this with out the REST Call data and URI requirements.

If the URI works from POSTMAN and from any browser, then something in the parameters or constructs of the "Make REST Call" is not the same. 

Run an interactive debug, and pull the variable value for the URL, Content Type, and Body variables and compare those, at the step in your script where the REST Call is made, to the test values used from the browser and / or POSTMAN tests; it will reveal this in the arguments being sent...  (Actually, I think the "Body" parameter is when using the POST method, so this may be blank???  test and see...). 

Verify your parameters are valid match case, context, and values for your URI arguments.

Something is not matching and therefore failing the criteria necessary for this web service. 

-Sean

[Mario C. G.]

Hi Sean,

The far end server engineer see in the logs this one:

Incorrect request protocol, requiered digest, request basic.

But I can not see where i can this.

Regards

Enviado desde mi ZTE de Telcel

[Sean Lynch]

If the HTTP request is supposed to be secured (did it change to HTTPS on your web browser and POSTMAN attempts?) you will need to follow the instructions for a secure SSL connection.  I am only seeing HTTP in your messages above. 

-Sean

[Mario C. G.]

Hi Sean,

Yes you have reason I am only using HTTP.

I make test from PostMan, and I use both Auth, firts whit Digest Auth and I received 200 code, after use Basic Auth and received 400 code.

Then the far end server only support Digest Auth. But with HTTP.

You know if UCCX can use Digest Auth? and If yes, can you help me to how change from Basic Auth to Digest Auth.

Regards

[Sean Lynch]

I believe only Basic Auth is supported. I do not have a quick reference handy to support this. Check the dev guide to verify.

-Sean