You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Intermittently Facing the issue when IISnode is responding 109 Pipe Error code in IIS logs. In my case IISnode failing with "iisnode failed to process http response status line" and "IIS node request processing failed for reason unrecognized by IIS side" . We are catching all the exception and there is no exception at node js end . Indeed sometime request is not even hitting to node js and if hit to node js application it works good and generate the output but IInode already responded with 500 error to client application . We have seen issue more frequently when input request body is too big .
The text was updated successfully, but these errors were encountered:
Intermittently Facing the issue when IISnode is responding 109 Pipe Error code in IIS logs. In my case IISnode failing with "iisnode failed to process http response status line" and "IIS node request processing failed for reason unrecognized by IIS side" . We are catching all the exception and there is no exception at node js end . Indeed sometime request is not even hitting to node js and if hit to node js application it works good and generate the output but IInode already responded with 500 error to client application . We have seen issue more frequently when input request body is too big .
The text was updated successfully, but these errors were encountered: