> From: gregames [mailto:gregames] On Behalf Of Greg Ames > > "Paul J. Reder" wrote: > > > > This looks exactly like the problem that Allan and I ran into when you > > tried to send a request to http://foo.bar.org:443 (i.e. insecure request > > over the secure port). It tried to generate an error and went into an > > infinte loop. > > Can you try that with current HEAD and let us know what happens?
While the problems were similar, they were not caused by the same code, and the SSL problem would not have been touched at all by this patch. The problem with mod_ssl was fixed a while ago, and it never touched the ap_die code. Basically, in mod_ssl's post_read_request phase, we check for a flag to determine if the request was HTTP over the HTTPS port. The problem is that if we find the flag, then we do an internal redirect, which also runs the post_read_request function. Because the flag wasn't cleared, we just returned another error, which caused another internal_redirect, which ran the same phase, etc. Ryan
