I had successfully deployed IIRF v2 with IIS 6.0 acting as SSL frontend to the backend Apache2 (XAMPP distribution) in Reverse Proxy mode.
However I experienced some troubles with dynamic PHP content served by Apache 2 and chunked encoding. Every time when I am accessing some dynamic PHP5 page with significant amount of dynamic content, it gets delivered from Apache to IIRF using chunked
encoding. No bugs or errors in Apache 2, PHP or IIRF logs.. And the content coming from Apache seems to be valid (as I can access Apache running on port 8081 directly just fine). But if I try accessing the same content thru IIRF, then all browsers (I tried
MSIE, FireFox and Chrome) are complaining and not displaying the page. Google Chrome tells something about the chunked encoding broken.. FireFox just doesn't display the page at all. Sorry, I have no sniffer trace since I was forwarding http to https and HttpFox
just didn't print out any content at the client side at all as if connection gets reset by IIRF...
So it seems like IIRF v2.0 ProxyPass breaks the chunked encoding at some point. The workaround I had to use: buffer the entire contents of dynamic page at PHP with ob_start() / ob_get_contents, calculate the size of the output buffer and prepend an
extra "Content-Length" header in PHP script itself before flushing the content to Apache.. Thus avoiding the chunked encoding to be sent by Apache to IIRF. No chunked encoding - no issue :)
Do I file it as a bug and do you need any extra information (sample contents) that gets broken by the IIRF in reverse proxy mode? I don't think it's a priority bug since I found a reasonable workaround for me, it works for me with the output buffering..
but it looks like the chunked encoding is fairly popular, it might not work well for someone else.
BTW, Thanks for the great software! It does exactly what I need.