Solved

HTTP Connector error: Specified value has invalid CRLF characters

  • 13 June 2023
  • 9 replies
  • 162 views
Harm Horstman
Rank
Userlevel 5
Badge +20

I try to get a process flow with HTTP connector running

I have tried a lot of things already, but still get this error:

Specified value has invalid CRLF characters.
Parameter name: value

Any suggestions on what can be the reason for this?

 

 

icon

Best answer by Roel 15 June 2023, 09:18

View original
This topic has been closed for comments

9 replies

V
Rank
Userlevel 6
Badge +4

Hello Harm,

This is not a lot of information to work with, but I suspect that you might be trying to do a multipart/form-data POST request and that you are not using correct new lines in the request body. CRLF stands for Carriage Return (\r) Line Feed (\n) (enters/new lines, in simple terms). For multipart/form-data requests you need specify a boundary that's place between each part of the request, followed by a carriage return and a line feed.

If you think this is not the cause of your issue, please provide some more information on the request that you are attempting to make. This error is not a general HttpConnector error, I'm pretty sure it has to be a mistake in the request body. The full error message, including stacktrace, will also help with determining that.

Harm Horstman
Rank
Userlevel 5
Badge +20

Hi Vincent,

Thanks for your response.

After 3 hours of trial and error, I just found out that the error does not appear in an earlier version (2023.1.13) of the Windows GUI.

The whole scenario is very basic and I have done this before, so I am quite sure that I did nothing wrong.

See the output of the debug screen of the control procedure that does the magic below:

EXEC prc_pf_save_week_activity_images_into_database_execute_tab_task_activity
     @execute_tab_task_activity_execute_logic_app = 1,
     @cal_year_week = '2023-23',
     @http_body = '{cal_year_week : "2023-23"}',
     @http_url = 'https://prod-247.westeurope.logic.azure.com:443/workflows/XXXXXXXXXXXXXXX/triggers/manual/paths/invoke?api-version=2016-10-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=VeAeJ9tqs_bhCDphPD-VScWwguuq-gkjSMxutUSA8dc'

http_body and http_url are both of type VARCHAR(MAX)
 

 

 

Roel
Rank
Userlevel 4
Badge +1

Hello Harm,


Do you use the exact same value for http_body parameter in the situation with the older Windows GUI? In that case this has to be a bug, although the code for setting the body value has not changed in a while. If this is the case then would you be so kind to file a ticket in TCP so we can make time to investigate this.

 

If your http_body value does indeed contain CRLF characters, which indicates line breaks like Vincent described, then you could try replacing them with </br>’s in the value of the http_body parameter, something like:

 

REPLACE(@http_body,CHAR(13)+CHAR(10),'</br>')

 

I hope this helps.

 

Kind Regards,

Roel

Harm Horstman
Rank
Userlevel 5
Badge +20

Hi Roel,

Ok, I will make a ticket in TCP. I have double checked everything and seen that it works fine with version 2023.1.13 and NOT with version 2023.1.16.

As I said the content (body) of my request is nothing more than:
{cal_year_week : "2023-23"}

 

Roel
Rank
Userlevel 4
Badge +1

Hi Roel,

Ok, I will make a ticket in TCP. I have double checked everything and seen that it works fine with version 2023.1.13 and NOT with version 2023.1.16.

As I said the content (body) of my request is nothing more than:
{cal_year_week : "2023-23"}

 


I noticed your json value key doesn't have quotes. Could that have anything to do with it?

It should be { “cal_year_week”: "2023-23”}

Harm Horstman
Rank
Userlevel 5
Badge +20

I have tried that also, but it does not make a difference:

 

Roel
Rank
Userlevel 4
Badge +1

Thanks for clarifying.

 

We will put this on our backlog and update the ticket in TCP accordingly.

 

Kind Regards,

Roel

 

 

Harm Horstman
Rank
Userlevel 5
Badge +20

Yes please, I hope it can be solves soon, so that we make use of latest releases

Harm Horstman
Rank
Userlevel 5
Badge +20

Hi @Roel, 

Any news about this, can you indicate when it will be resolved?

Terms & ConditionsCookie settings