<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [Web-SIG] WSGI input filter that changes content length.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Graham Dumpleton wrote:<BR>
> My understanding is that content encoding is different<BR>
> to transfer encoding, ie., is not hop by hop in this<BR>
> sense and that the same statements don't apply.<BR>
<BR>
No, you're right. "Content-Encoding: gzip" is not hop-by-hop, and should therefore be allowed in middleware. But as you've noticed, that doesn't mean it's easy. ;)<BR>
<BR>
<BR>
Robert Brewer<BR>
System Architect<BR>
Amor Ministries<BR>
fumanchu@amor.org<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>