After recent changes, the proxying of "CONNECT host:port HTTP/1.0" requests
(as are issued by current browsers for https://host/ URLs) ceased to work. Now the request method is parsed early and used to decide which of two URI parsing routines should be used (either the full scheme://user:port@host... format, or the fixed host:port format for CONNECTs). Yet to fix: the request method is currently determined twice. "Probably" the later check is redundant (but I'm not sure because of the difficult logic with internal subrequests etc.) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@80785 13f79535-47bb-0310-9956-ffa450edef68
parent
7745a538
Please register or sign in to comment