I understand. But isn't the ap_read_request HTTP specific given it's creating the request and all? In other words, if protocol is HTTP, we let connection filter know about the request. If not, we don't. That to me sounds exactly the same as your suggestion.
I must be missing something... Bojan Quoting [EMAIL PROTECTED]: > You don't want to do this. A connection based filter is connection > oriented. By definition, it has no concept of a request. While this > might make sense for HTTP, other protocol modules will have a much harder > time with this change. > > Ryan ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/
