In theory, we now correctly implement all of the FastCGI protocol, so
there's no reason that request ids wouldn't be matching up. Until we see an example of a request id mismatch error that is absolutely not caused by an error in our parsing of the FastCGI protocol, we should be able to go back to treating mismatches as errors. * modules/proxy/mod_proxy_fcgi.c (dispatch): Remove #ifdef that turned off treating rid mismatches as fatal errors. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/fcgi-proxy-dev@366985 13f79535-47bb-0310-9956-ffa450edef68
parent
f50f6796
Please register or sign in to comment