SAP Webdispatcher Http 400 Bad Request

[Former Member]

Hi All,

I am getting the below error when my SFDC system is trying to send a Http request to Webdispatcher.

Out of 10 request 8 get a Http 200 success response and 2 go to Http 400 Bad request.

Could you let me know what could be the cause of the error:

400 Bad HTTP request

Bad HTTP request

Error: -21

Version: 7011

Component: HTTP_FILTER

Date/Time: Wed Jun 22 18:57:56 2011

Module: http_auth_mt.c

Line: 584

Server: my server

Error Tag:

Detail: illegal request

Thx in advance

Ravijeet

[Former Member]

Hello All,

can any body help on this issue ?

issue :

After  doing a copy paste from a email into Notes of my service ticket ,when i click on partner tab i get 400 bad http request .

error details :

400 Bad HTTP request

Bad HTTP request

--------------------------------------------------------------------------------

Error: -21

Version: 7200

Component: HTTP_FILTER

Date/Time: Fri Nov 23 16:26:37 2012 

Module: http_auth.c

Line: 590

Server: LCCCRMDEV001_LCD_00

Error Tag: {00042955}

Detail: illegal request

i was checking my ICM Monitor log ,and found

[Thr 1872] *** ERROR => URLDecode recognised invalid sign in form field [ictxxfilt.c  256]

[Thr 1872] *** ERROR => illegal request {00054c40} [http_auth.c 590]

this issue has come up only after our recent Kernel Upgrade .

currently we have CRM 7.0.

Internet Communication Manager Version 7.20, multithreaded, ASCII, 64 BIT

kernel information
system name      = LCD
kernel release   = 720
database library =
compiled on      = NT 5.2 3790 S x86 MS VC++ 14.00
compile time     = Jul  8 2012 19:08:28
update level     = 0
patch number     = 222
source id        = 0.300

SAP/webcuif services are active .

i have looked into possible Notes corresponding to this issue ,but our patch level is significantly higher than mentioned in relevant sap notes.

0001602853

0001719203

0001348980

0000925602

0000864878

can any body throw some light on  possible cause of this issue ?

[Former Member]

We have the same issue, after 7.02 upgrade of SAP NW Portal. Did you solved the problem?

[Former Member]

Hi

we also faced with this issue. have you found out a solution?

[Former Member]

Hi All,

I looked further in the trace files and I see below error lines:

[Thr 1087400288] *** ERROR => URLDecode recognised invalid sign in form field [ictxxfilt_mt 249]

[Thr 1087400288] *** ERROR => illegal request [http_auth_mt.c 494]

[Thr 1087400288] IcmPlCheckRetVal: Plugin retval: PLUGIN_RET_ERROR (701)

[Thr 1087400288] *** ERROR => NiIRead: SiRecv failed for hdl 7 / sock 12

[Thr 1087400288] *** ERROR => URLDecode recognised invalid sign in form field [ictxxfilt_mt 249]

[Thr 1087400288] *** ERROR => illegal request [http_auth_mt.c 494]

[Thr 1087400288] IcmPlCheckRetVal: Plugin retval: PLUGIN_RET_ERROR (701)

Thx in advance

Ravijeet

[Former Member]

Hi All,

Any suggestions ??

The calling SFDC used java code to make a http call

The SFDC basically uses the following code to make the call to webdispatcher each time. If you see they are using the hardcoded endpoint each time SFDC calls SAP through a SAP request.

//http version

HttpRequest req = new HttpRequest();

HttpResponse res = new HttpResponse();

Http http = new Http();

String myendpoint = 'http://111.22.234.789:8117/sap/xi/adapter_plain?namespace=urn%3Asfdc-com%3AINF001%3ASFDC&interface=SIOS_SF_Trig&service=BC_SFDC&party=&agency=&scheme=&QOS=EO&sap-user=SFDC_USR&sap-password=sfdcsapxiuser&sap-client=250&sap-language=ENsap-user=SFDC_USR&sap-password=sapxiuser';

String thexmlbody ='<?xml version="1.0" encoding="UTF-8"?><ns0:MT_SF_Req xmlns:ns0="urn:sfdc-com:INF001:SFDC_Start"><SAPID>'ID'</SAPID><ACTION>'ACTION'</ACTION&g t;</ns0:MT_SF_Req>';

req.setEndpoint(myendpoint);

req.setMethod('POST');

req.setBody(thexmlbody);

req.setCompressed(true); // otherwise we hit a limit of 32000

res = http.send(req);

Is it becoz of the HTTP Url we are using ? What is the exact sysntax for sender Http Url ? What is the max size of a Http request ??

Thx in advance

Ravijeet

Edited by: RAVIJEET.SAP.PI on Jun 27, 2011 5:45 PM

[naveen_chichili]

Hi Ravijeth,

this normally occurs because of large files/Huge message flow please go through SAP Notes-824554, 906435, 783515, 910649, 706563

Regards,

Naveen

[Former Member]

Hi Naveen,

I checked the message and saw the size as 228 bytes. We tried to capture the HTTP message out of DMZ before it hits the SAP Webdipsatcher. The size of a successful http 200 request and 400 bad request is similar. I am unable to determine for what reason the message goes to HTTP 400 Bad Request.

Do we require any optimum configuration on the webdipsatcher side or increase some timeout, buffer etc ?

Thx in advance

Ravijeet