IISProxy.dll:502 Bad Gateway - Failed to read response header

[Former Member]

Hello,

we have not made the jump over to the web dispatcher yet and are still using the IISProxy.dll for our ISA implementation on the WAS 6.40. From time to time we get reports of users saying they have the message "IISProxy.dll:502 Bad Gateway" on their screens in different frames, not always the same one.

When we match up the times in the IisProxy_*.log files we see the message: "Proxy E Failed to read response header." The users do not always get this message and it happens across the different applications we have deployed (i.e. b2b & b2c).

Has anyone else come across this issue? If so what might be the resolution? Due to it's unpredictable nature we have not been able to re-create the issue in our test environments to troubleshoot.

Any help is appreciated.

Regards,

Will

[Former Member · Accepted solution]

Hi,

The problem is because of the keepalive timeout differences between IIS and the J2EE server (HTTP provider)

read this notes :

1.820028

2.713568 symptom 18

3 also read this /thread/56476 [original link is broken]