Topic
3 replies Latest Post - ‏2013-07-25T04:05:41Z by cmari
cmari
cmari
4 Posts
ACCEPTED ANSWER

Pinned topic HTTP Response code 400

‏2013-02-05T05:46:05Z |
We have a WSP service with a set of request, response and error rules. And we have set Process backend errors to OFF. Recently we upgraded the firmware version to 3.8.2.14 (from 3.8.2.0). Post that we found an issue in all error responses sent back (by error rule) to the clients, the protocol response code is set to 400. Because of this most of the SOAP clients are not able to parse the response message.

Some data collected from probe and client response.

Input context of error rule
var://service/error-code string 0x00d30003
var://service/error-headers string 'HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
X-Backside-Transport: FAIL FAIL
Connection: close'

Output context of error rule
var://service/error-code string 0x00d30003
var://service/error-headers string 'HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
X-Backside-Transport: FAIL FAIL
Connection: close'

Response header received in the client
Firmware: 3.8.2.14
HTTP/1.1 400 Error
Content-Type: text/xml
X-Backside-Transport: FAIL FAIL
Connection: close

Whereas in the previous firmware we are getting 500 response code, for the same configuration.
Response header received in firmware 3.8.2.0
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
X-Backside-Transport: FAIL FAIL
Connection: close

Tested in the latest fixpack (3.8.2.17) also, getting 400 response only.

Any suggestions to solve this issue?