--On Monday, March 1, 2004 11:57 PM -0800 Stas Bekman [EMAIL PROTECTED] wrote:
AP_FTYPE_PROTOCOL. But what difference does it make as long as it sees the
HTTP headers?
Because AP_FTYPE_PROTOCOL is request-level when you are using HTTP.
But, you should not be changing HTTP headers in a filter.
Justin Erenkrantz wrote:
--On Monday, March 1, 2004 11:57 PM -0800 Stas Bekman [EMAIL PROTECTED]
wrote:
AP_FTYPE_PROTOCOL. But what difference does it make as long as it sees
the
HTTP headers?
Because AP_FTYPE_PROTOCOL is request-level when you are using HTTP.
yes, but it won't see the
Stas Bekman wrote:
If I'm inside an input connection filter and want to be able to tell one
HTTP request from another what should I do? Counting Content-length is
ineffective, and a won't work if C-L header is wrong.
I can tell the end of HTTP headers section from the request body, by
matching
--On Monday, March 1, 2004 8:18 PM -0800 Stas Bekman [EMAIL PROTECTED] wrote:
Answering my own question, the solution is to use conn-keepalives counter
which is incremented at the end of each request. By storing the previous
count and comparing with the current count one can tell when a new
Justin Erenkrantz wrote:
--On Monday, March 1, 2004 8:18 PM -0800 Stas Bekman [EMAIL PROTECTED]
wrote:
Answering my own question, the solution is to use conn-keepalives
counter
which is incremented at the end of each request. By storing the previous
count and comparing with the current count
* Stas Bekman [EMAIL PROTECTED] wrote:
Why should a connection-level filter know about HTTP requests? --
justin
Because that's the only way to write a filter that processes HTTP headers
only.
Hmm. FTPYPE_PROTOCOL (sp?) is for such a purpose. If it's no applicable,
we'd need to fix
Andr Malo wrote:
* Stas Bekman [EMAIL PROTECTED] wrote:
Why should a connection-level filter know about HTTP requests? --
justin
Because that's the only way to write a filter that processes HTTP headers
only.
Hmm. FTPYPE_PROTOCOL (sp?) is for such a purpose. If it's no applicable,
we'd need
If I'm inside an input connection filter and want to be able to tell one HTTP
request from another what should I do? Counting Content-length is ineffective,
and a won't work if C-L header is wrong.
I can tell the end of HTTP headers section from the request body, by matching
/^[\r\n]$/ while
