On Thu, 18 Jun 2009 11:13:00 -0600 (MDT) "Lyudmila L. Balakireva" <ludab@xxxxxxxx> wrote: > > > > > > On 17 Jun 2009, at 18:52, Lyudmila L. Balakireva wrote: > > > >> Hello, > >> I am new to apache and c and > > > > Then you're probably being over-ambitious :-) > > > > One thing that immediately stands out: you're using the request > > pool, but you defined your filter to run outside the protocol > > level, where the request object (and hence its pool) is no longer > > valid. The simple fix would be to use the connection pool. But > > that in turn highlights the likelihood that you might want to > > revisit your architectural design. > > thank you for you reply, though the fact that I am using request > when it is no longer valid, already occurred to me yesterday, That's impressive for a self-professed newbie! I take it you're not new to programming, only to C? > could > you tell more what you mean > "But that in turn highlights the likelihood that you might want to > revisit your architectural design. .".. ? > Do I need to move to AP_FTYPE_RESOURCE filter or you mean overall > approach is not valid (opening socket per request for example is not > good)? Maybe. I'd need to know more about your problem, and spend more think-time, to elaborate on that (don't tell me - I don't have time to go into it). What are you trying to capture? If response headers, grab them from the headers_out and err_headers_out tables. If you want to catch data, bear in mind that things like mod_deflate and mod_charset run at CONTENT_SET, so you may want to run before that. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|