Beta 3 includes the host fix.
Apache connect now works! Trying with Beta 4.
I tried forcing a CONNECT through the Apache webproxy to see what it would do - unsurprisingly, didn't get far (far-end service is HTTP, not HTTPS). However I noticed the Host header field may be being incorrectly set, From a Wireshark session:
CONNECT bbcmedia.ic.llnwd.net:80 HTTP/1.1
Host: proxyaddress
AIUI the Host should normally be the requested far-end resource (e.g., "Host: bbcmedia.ic.llnwd.net"). I think the reason it's working now is because Apache is seeing the Host header, but it's not strictly validating it. I think it might cause issues if an HTTPS resource is requested which uses SNI to determine certificate validity...
Comparing fb2k with a few other requests from same wireshark session:
CONNECT www.ipchicken.com:443 HTTP/1.1
Host: www.ipchicken.com:443
GET http://http.00.s.sophosxl.net/V3/01/cynl.tbbtyr.pbz.m/ HTTP/1.1
Cache-Control: no-cache
Pragma: no-cache
User-Agent: SXL/3.1
Proxy-Connection: Keep-Alive
Host: http.00.s.sophosxl.net
CONNECT play.google.com:443 HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:65.0) Gecko/20100101 Firefox/65.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: play.google.com:443
Thanks for your hard work so far, and for implementing a fix and a new feature so quickly! Very impressive once again
The force HTTP CONNECT option I will try out with some HTTPS resources and report back.