<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi all<br>
<br>
I got my modifying reverse proxy working by adding <br>
<br>
proxy_set_header Accept-Encoding '';<br>
<br>
before my body_filter_by_lua code block. This way I force the proxy to give me uncompressed data, and then the lua code works perfectly. I'll add a gzip on; at the end, to pass the data to the browser compressed.<br>
<br>
Thanks<br>
<br>
Bart<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF15484"><font color="#000000" face="Tahoma" size="2"><b>From:</b> nginx-bounces@nginx.org [nginx-bounces@nginx.org] on behalf of Bart van Deenen [Bart.vanDeenen@spilgames.com]<br>
<b>Sent:</b> Thursday, November 29, 2012 11:37 AM<br>
<b>To:</b> nginx@nginx.org<br>
<b>Subject:</b> does body_filter_by_lua get called when proxied server returns gzipped data?<br>
</font><br>
</div>
<div></div>
<div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">Hi<br>
<br>
I posted the recent thread on problems with body_filter_by_lua, and I think it finally has to do with the fact that my browser allows gzipped data, and the server in my example returns gzipped data. I only found out using wireshark.<br>
<br>
Could it be that the gzipped data don't even reach the lua code?<br>
<br>
Thanks<br>
<br>
Bart<br>
</div>
</div>
</div>
</div>
</body>
</html>