DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20945>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20945

Mod_ext_filter mangles SSI





------- Additional Comments From [EMAIL PROTECTED]  2003-06-21 20:52 -------
> I don't know what you mean by a problem with a filter being
> "called for each piece" though.  mod_ext_filter will write data
> to the external filter as it receives it, so if the content
> generator or another filter sends it down in relatively small pieces,
> mod_ext_filter will write it to the external filter in the same
> relatively small pieces.  The amount of data received by the external
> filter in one piece is also limited by the amount of data the kernel
> will buffer for a pipe.

Tweak the slowdown filter so that it calls "cat -n" once on all files.  This
adds line numbers to Apache's output.  The config is:
  ExtFilterDefine slowdown mode=output cmd="/bin/cat -n" preservescontentlength
  <Location />
  SetOutputFilter slowdown
  </Location>

Next, view source on the test.shtml page as described above (though with the
include expanded to "sub.html" so that it works correctly).  The source looks
like this:

     1  <html><head><title>Title</title></head><body>
     2  <h1>Start</h1>
     3  <h3>[     1     This is the include.  <== NOTE THE "1" LINE NUMBER
     4  ]</h3>
     5  <h1>End</h1>
     6  </body></html>

As you can see from the line numbers created by "cat -n", the filter was run
twice; once on each peice of the page.  Then the two peices were spliced
together my mod_include.  In bug 20946 I argue that the SSI splicing should
occur before the filter.  That way the filter would only be run once and would
be able to see the whole page in context.

I hope these two posts answer your questions.  Let me know if I can provide any
more information.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to