Antwort: [Mod_gzip] SEND_AS_IS:RESPONSE_CONTENT_TYPE_EXCLUDED

mod_gzip@lists.over.net mod_gzip@lists.over.net
Wed, 29 Jan 2003 13:41:38 +0200


Hallo Markus,


> The mod_gzip.log file lists a lot of 'errors' like:

none of these is an "error".

> GET /webtogo/tutorial/ToDoList.jsp HTTP/1.1" 200 -
> mod_gzip: SEND_AS_IS:RESPONSE_CONTENT_TYPE_EXCLUDED In:0 -< Out:0 = 0%

You either explicitly excluded this Content-Type, or you didn't
exclude it. At least, mod_gzip didn't find an include rule firing
in rule evaluation phase 2.

> GET /webtogo/WLTop/server HTTP/1.1" 200 -
> mod_gzip: SEND_AS_IS:NO_CONTENT_TYPE_IN_RESPONSE_HEADER In:0 -< Out:0 =
0%

Your content does not contain any Content Type.
Thus it will be impossible to make mod_gzip let any include rule
fire for this response.

> GET /webtogo/dummy.html HTTP/1.1" 200 -
> mod_gzip: SEND_AS_IS:NO_200 In:0 -< Out:0 = 0

Uh - this one looks strange. Apache sent a HTTP-200 but mod_gzip
says NO_200? I have never seen anything like this before.

> Can't mod_gzip compress output from the web-to-go handler?

This depends on how this output works and how you configure mod_gzip.

 > mod_gzip_maximum_inmem_size   1000000

 You won't get more than 60000 (this is hard-coded in the source).

 > mod_gzip_item_include         handler    !cgi-script$
 > mod_gzip_item_include         handler    !cgi-script
 > mod_gzip_item_include         handler    !web-to-go$
 > mod_gzip_item_include         handler    !web-to-go

 What is this exclamation mark going to mean?

  > mod_gzip_item_include         file       ^^text/jsp$
  > mod_gzip_item_include         handler    !text/jsp$

  These two rules don't make any sense to me.



I don't see anything that is particularly broken in this configuration,

but to make your requests be compressed it would be necessary to know

more about the response to these requests - like inspecting them with


     http://www.schroepl.net/cgi-bin/http_trace.pl

or some tool of this type.

If you create content without a Content Type not only mod_gzip will get
into trouble but some UserAgents as well; if you send strange Content
Types you may simply have missed to write the corresponding include rules.

Viele Grüße

      Michael