Or, you can inject your own custom BIO layer. This is quite tricky to do (correctly), which is why most content filters are written for Apache 2.0 or later.
Bill Taisuke Yamada wrote: > IIRC, you can do it by pointing > > r->connection->client->fd > r->connection->client->fd_in > > to filtered content. > > Obviously, you'd need to save actual socket descriptors > somewhere, and do IO operations and descriptor swapping > at certain stage - probably at fixup and logging. Also, > you will need to modify several HTTP headers (like > Content-Length: and Transfer-Encoding:) before sending out > final response. > >>> I've currently got an Apache 2.0 module parsing headers and content for >>> inbound and outbound data using filters. I'd like to do something similar >>> with Apache 1.3. >>> >>> What is the preferred way to transform inbound and outbound content on 1.3? >>> It looks like nothing touches the data after a handler has been chosen. >>> >>> Is there at least an ugly hack to get this kind of functionality? > > -- > Taisuke Yamada <[EMAIL PROTECTED]>, http://rakugaki.org/ > 2268 E9A2 D4F9 014E F11D 1DF7 DCA3 83BC 78E5 CD3A > > Message to my public address may not be handled in a timely manner. > For a direct contact, please use my private address on my namecard.
