Gzipping proxied content after using subs_filter fails

[abstein2]

It looks like there's an issue with the newest revision of the module
and nginx 1.2.3. When installed, whether gzip is on or off, the portion
of code that was previously missing/not transmitted now gets
transmitted, but isn't the actual page content. Instead it's gibberish
with some of the raw nginx configuration mixed in. 

An example of the code being output:

Xv±t™Xv±t™ ý ý w.google-analytics.com/urchin.js"
type="text/javascript"> ct.asp">CONTACT US | PRIVACY POLICY | TERMS OF
USE
ccel-expires
x-accel-charset
x-accel-redirect
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirect¨Æ½
/usr/scgi_temp@ǽ€Ç½ÀǽȽ@Ƚ
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirectɽ
/usr/scgi_tempÀɽʽ@ʽ€Ê½Àʽ
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirecth˽
/usr/scgi_temp̽@̽€Ì½À̽ͽ
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirectÈͽ
/usr/scgi_temp€Î½ÀνϽ@Ͻ€Ï½
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirect(н
/usr/scgi_tempÀнѽ@ѽ€Ñ½Àѽ
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirectˆÒ½
/usr/scgi_temp@Ó½€Ó½ÀÓ½Ô½@Ô½
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirectèÔ½
/usr/scgi_temp€Õ½ÀÕ½Ö½@Ö½€Ö½
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirectH×½
/usr/scgi_tempؽ@ؽ€Ø½ÀؽÙ½
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirect¨Ù½
/usr/scgi_temp@Ú½€Ú½ÀÚ½Û½@Û½
status
x-accel-buffering
x-accel-limit-rate
x-accel-expires
x-accel-charset
x-accel-redirectܽ


The actual HTML code does show up after a block of text like the one
above, but it begins mid-string as though it must be a completely new
chunk in the buffer. All subs_filter replacements have already occurred
by the time it reaches the gibberish block.

Using 1.2.1 along with an older version of the module seems to work
properly as Maxim had suggested. I'm happy to help continue to test this
in any way possible.

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,229545,229616#msg-229616