|
Failed to Process Response Headers
|
|
Replies:
3
-
Pages:
1
-
Last Post:
Nov 6, 2009 2:55 AM
Last Post By: ebengtso
|
|
|
Posts:
54
Registered:
Nov 14, 2007 09:48:20 AM
|
|
|
|
Failed to Process Response Headers
Posted:
Dec 18, 2008 05:46:04 AM
|
|
|
|
Can someone shed some light on the error message "Failed to process response headers". We often used to face this error message when we try to hit the target web service. And same request will process fine if we trigger again.
Not sure why we are able to see intermittent issues with the message "Failed to process response headers"
Regards,
Suresh Sanga
|
|
Posts:
519
Registered:
Oct 26, 2007 12:34:15 AM
|
|
|
|
Re: Failed to Process Response Headers
Posted:
Dec 18, 2008 01:56:45 PM
in response to: SangaS's post
|
|
|
|
This means that your device tried to use an established TCP persistent connection to the target - but when data was posted it just received a TCP RST instead of a response packet. This has to do with poor TCP persistent connection handling between the device and the back end.
If this is a significant issue, the best thing to do is to force HTTP 1.0 and disallow persistent connections on the back side of your DataPower SERVICE. Look in the Objects > Service Type screen for the best set of options to control HTTP version and persistent connections. On a healthy backbone network there is really very little cost to TCP session creation so you will not notice the performance difference.
Corey
|
|
Posts:
54
Registered:
Nov 14, 2007 09:48:20 AM
|
|
|
|
Re: Failed to Process Response Headers
Posted:
Dec 18, 2008 11:44:53 PM
in response to: cscobie's post
|
|
|
|
Thanks Corey. Useful information to configure WSP with HTTP 1.0 and HTTP 1.1.
Regards,
Suresh Sanga
|
|
Posts:
105
Registered:
Oct 19, 2005 03:53:09 PM
|
|
|
|
Re: Failed to Process Response Headers
Posted:
Nov 06, 2009 02:55:31 AM
in response to: SangaS's post
|
|
|
|
Just as completeness for those who have the issue "Failed to Process Response Headers".
This issue also occurs when the backend is listening on HTTPS and the configuration in datapower of the remote server is set as HTTP. This is not an intermittent error, and is caused by the SSL handshake.
|
|
|
|
|
