From 4974a83fb1252e906d2f7a554188f40807b777f6 Mon Sep 17 00:00:00 2001 From: ParagHurkat <49488006+ParagHurkat@users.noreply.github.com> Date: Fri, 13 Mar 2026 19:45:57 +0530 Subject: [PATCH] Update troubleshooting steps for CGI application errors Clarified error message and added example FREB output for troubleshooting. --- ...troubleshoot-502-2-bad-gateway-error-in-cgi-apps.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/support/developer/webapps/iis/site-behavior-performance/troubleshoot-502-2-bad-gateway-error-in-cgi-apps.md b/support/developer/webapps/iis/site-behavior-performance/troubleshoot-502-2-bad-gateway-error-in-cgi-apps.md index 495ab70ac14..b0c217b1dd0 100644 --- a/support/developer/webapps/iis/site-behavior-performance/troubleshoot-502-2-bad-gateway-error-in-cgi-apps.md +++ b/support/developer/webapps/iis/site-behavior-performance/troubleshoot-502-2-bad-gateway-error-in-cgi-apps.md @@ -35,7 +35,7 @@ This problem occurs because the CGI process terminates unexpectedly before the C When sending a request to a CGI application running via IIS, the user is presented with the following error instead of the expected response: -> The specified CGI application misbehaved by not returning a complete set of HTTP headers +> The specified CGI application misbehaved by not returning a complete set of HTTP headers. Capture a [Netmon](/windows-hardware/drivers/portable/using-the-netmon-tool) trace. It shows: @@ -78,7 +78,13 @@ HTTP: Data: Number of data bytes remaining = 232 (0x00E8) 001A0: 3E 3C 2F 68 74 6D 6C 3E > ``` -Capture [FREB](../health-diagnostic-performance/troubleshoot-php-with-failed-request-tracing.md) log for the HTTP error message and locate which module is throwing this error message. +Capture [FREB](../health-diagnostic-performance/troubleshoot-php-with-failed-request-tracing.md) log for the HTTP error message and locate which module is throwing this error message. Example FREB output + +> MODULE_SET_RESPONSE_ERROR_STATUS +> ModuleName="CgiModule" +> Notification="EXECUTE_REQUEST_HANDLER" +> HttpStatus="500" +> HttpReason="Internal Server Error" Troubleshoot the CGI process executable file to determine why the CGI process terminates unexpectedly. You might have to generate a memory dump file of the CGI process when the access violation occurs.