mod_deflate problem with chunked encoding

[Philip Mak <pm...@animeglobe.com>]

The following webpage on a mod_deflate enabled server is not working
correctly in some browsers:

http://www.aaanime.net/pmak/sylphiel/

If I "telnet www.aaanime.net 80" and send the following commands:

GET /pmak/sylphiel/ HTTP/1.1
Host: www.aaanime.net
Accept-Encoding: gzip

then the data it sends back is partially gzip, and partially plain
text! It is sent with "Transfer-Encoding: chunked" and the first 1 or
2 chunks are gzipped, but the rest are not.

The source code for the page is an .shtml file. Inside that .shtml
file, I have the directive <!--#exec cgi="navbar.cgi"-->. Everything
until after that directive is gzipped, then the rest of it is not.

navbar.cgi is a simple perl script that does:
print "Content-type: text/html\n\n";

followed by a few more "print" statements.

Any idea how to fix this problem? Do I need to provide any additional
information in particular? Thanks.

Re: mod_deflate problem with chunked encoding

[Stas Bekman <st...@stason.org>]

Ron Savage wrote:

> Stas
> 
> Does the senario doc (below) apply to Apache V 1, V2 or both?


only v1 at this point.


>>here: http://perl.apache.org/guide/scenario.html, please do that. But 

there is a whole new tree of docs for apache/2.0 modperl/2.0 docs in 
works. Stay tuned.

_____________________________________________________________________
Stas Bekman             JAm_pH      --   Just Another mod_perl Hacker
http://stason.org/      mod_perl Guide   http://perl.apache.org/guide
mailto:stas@stason.org  http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/

Re: mod_deflate problem with chunked encoding

[Ron Savage <ro...@savage.net.au>]

Stas

Does the senario doc (below) apply to Apache V 1, V2 or both?

Cheers
Ron Savage
ron@savage.net.au
http://savage.net.au/index.html

> here: http://perl.apache.org/guide/scenario.html, please do that. But 

Re: mod_deflate problem with chunked encoding

[Stas Bekman <st...@stason.org>]

Jeremy Howard wrote:

> Geoffrey Young wrote:
> 
>>Philip Mak wrote:
>>
>>>>>The following webpage on a mod_deflate enabled server is not working
>>>>>correctly in some browsers:
>>>>>
> <...>
> 
>>a few of us have been wondering where all the traffic on these modules
>>has been coming from, is all - I thought it might genuinely be some
>>mis-documentation or something...
>>
>>
> I originally introduced these modules to this list in an earlier post titled
> "Report on mod_accel and mod_deflate" in which I promoted these modules as
> an excellent tool for creating a front-end accelerator to mod_perl web
> applications. It included brief documentation for installing and configuring
> the modules--previously there had only been Russian documentation.
> 
> There's been no other location for English language discussion of these
> modules. So the discussion has ended up here. I take full responsibility for
> any OT pollution as a result. ;-)
> 
> Given that these modules are new, don't have an active discussion home in
> English yet, and are very relevent to mod_perl programmers, I'd like to see
> discussion remain here, or at least have Igor post the occassional update on
> new releases etc.
> 
> If that bothers anyone then I'm happy to set up a mailing list elsewhere, of
> course.

As with any discussion that tend to recurr (what Doug used to call 'a 
broken record'), it's better to sum up things, adds them to 'some' guide 
and then make long threads short, by sending what seems to be hated by 
everyone: 'read the guide' + direct URL if not too lazy.

So if you want to send me some short instructions which can be plugged 
here: http://perl.apache.org/guide/scenario.html, please do that. But 
first run the submitted doc through the list, for polishing. Once it's 
done I'll add them to the mod_perl guide.

_____________________________________________________________________
Stas Bekman             JAm_pH      --   Just Another mod_perl Hacker
http://stason.org/      mod_perl Guide   http://perl.apache.org/guide
mailto:stas@stason.org  http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/

Re: mod_deflate problem with chunked encoding

[Igor Sysoev <is...@rambler-co.ru>]

On Fri, 18 Jan 2002, Jeremy Howard wrote:

> Geoffrey Young wrote:
> > Philip Mak wrote:
> > >>>The following webpage on a mod_deflate enabled server is not working
> > >>>correctly in some browsers:
> <...>
> 
> > a few of us have been wondering where all the traffic on these modules
> > has been coming from, is all - I thought it might genuinely be some
> > mis-documentation or something...
> >
> I originally introduced these modules to this list in an earlier post titled
> "Report on mod_accel and mod_deflate" in which I promoted these modules as
> an excellent tool for creating a front-end accelerator to mod_perl web
> applications. It included brief documentation for installing and configuring
> the modules--previously there had only been Russian documentation.
> 
> There's been no other location for English language discussion of these
> modules. So the discussion has ended up here. I take full responsibility for
> any OT pollution as a result. ;-)
> 
> Given that these modules are new, don't have an active discussion home in
> English yet, and are very relevent to mod_perl programmers, I'd like to see
> discussion remain here, or at least have Igor post the occassional update on
> new releases etc.

As to mod_deflate I think mod_perl list is not right place to discuss it.
But mod_accel discussion is more relevent to this list as well as
lingerd, mod_proxy, Squid and other reverse proxing or accelerating
technology.

> If that bothers anyone then I'm happy to set up a mailing list elsewhere, of
> course.

I think it would be nice.

Igor Sysoev

Re: mod_deflate problem with chunked encoding

[Jeremy Howard <jh...@fastmail.fm>]

Geoffrey Young wrote:
> Philip Mak wrote:
> >>>The following webpage on a mod_deflate enabled server is not working
> >>>correctly in some browsers:
<...>

> a few of us have been wondering where all the traffic on these modules
> has been coming from, is all - I thought it might genuinely be some
> mis-documentation or something...
>
I originally introduced these modules to this list in an earlier post titled
"Report on mod_accel and mod_deflate" in which I promoted these modules as
an excellent tool for creating a front-end accelerator to mod_perl web
applications. It included brief documentation for installing and configuring
the modules--previously there had only been Russian documentation.

There's been no other location for English language discussion of these
modules. So the discussion has ended up here. I take full responsibility for
any OT pollution as a result. ;-)

Given that these modules are new, don't have an active discussion home in
English yet, and are very relevent to mod_perl programmers, I'd like to see
discussion remain here, or at least have Igor post the occassional update on
new releases etc.

If that bothers anyone then I'm happy to set up a mailing list elsewhere, of
course.

Re: mod_deflate problem with chunked encoding

[Igor Sysoev <is...@rambler-co.ru>]

On Thu, 17 Jan 2002, Geoffrey Young wrote:

> Philip Mak wrote:
> 
> > On Thu, Jan 17, 2002 at 07:38:17PM -0500, Geoffrey Young wrote:
> > 
> >>Philip Mak wrote:
> >>
> >>
> >>>The following webpage on a mod_deflate enabled server is not working
> >>>correctly in some browsers:
> >>>
> >>[OT stuff snipped]
> >>did you email the right list?
> >>
> > 
> > I figured that the mod_perl mailing list was the best place to post
> > about these problems, since mod_deflate/mod_accel doesn't have its own
> > mailing list and there's a lot of people on this list who use it...

If you have mod_accel/mod_deflate problem feel free contact me directly.

Igor Sysoev

Re: mod_deflate problem with chunked encoding

[Geoffrey Young <ge...@modperlcookbook.org>]

Philip Mak wrote:

> On Thu, Jan 17, 2002 at 07:38:17PM -0500, Geoffrey Young wrote:
> 
>>Philip Mak wrote:
>>
>>
>>>The following webpage on a mod_deflate enabled server is not working
>>>correctly in some browsers:
>>>
>>[OT stuff snipped]
>>did you email the right list?
>>
> 
> I figured that the mod_perl mailing list was the best place to post
> about these problems, since mod_deflate/mod_accel doesn't have its own
> mailing list and there's a lot of people on this list who use it...


that's fine - you don't have to justify the post to me :)

a few of us have been wondering where all the traffic on these modules 
has been coming from, is all - I thought it might genuinely be some 
mis-documentation or something...

--Geoff

Re: mod_deflate problem with chunked encoding

[Geoffrey Young <ge...@modperlcookbook.org>]

Philip Mak wrote:

> The following webpage on a mod_deflate enabled server is not working
> correctly in some browsers:


[OT stuff snipped]


did you email the right list?

I'm not sure why mod_deflate and mod_accel problems keep popping up here 
of late, but maybe there's some mis-information floating around 
somewhere in the docs on these two modules?

not that this list is opposed to OT but interesting discussion from time 
to time :)

--Geoff

Re: mod_deflate problem with chunked encoding

[Igor Sysoev <is...@rambler-co.ru>]

On Thu, 17 Jan 2002, Philip Mak wrote:

> The following webpage on a mod_deflate enabled server is not working
> correctly in some browsers:
> 
> http://www.aaanime.net/pmak/sylphiel/
> 
> If I "telnet www.aaanime.net 80" and send the following commands:
> 
> GET /pmak/sylphiel/ HTTP/1.1
> Host: www.aaanime.net
> Accept-Encoding: gzip
> 
> then the data it sends back is partially gzip, and partially plain
> text! It is sent with "Transfer-Encoding: chunked" and the first 1 or
> 2 chunks are gzipped, but the rest are not.
> 
> The source code for the page is an .shtml file. Inside that .shtml
> file, I have the directive <!--#exec cgi="navbar.cgi"-->. Everything
> until after that directive is gzipped, then the rest of it is not.
> 
> navbar.cgi is a simple perl script that does:
> print "Content-type: text/html\n\n";
> 
> followed by a few more "print" statements.
> 
> Any idea how to fix this problem? Do I need to provide any additional
> information in particular? Thanks.

The problem really exists. I suspect '<!--#exec' although '<!--#include'
works fine on our several sites. I'll try to repeat it in my local
enviroment.

Igor Sysoev