Help on extracting http header

Hi
I hope this is the right group for this, or would you point me to the
proper group for this. We are developing an application for allowing/
denying packets and billing. We are using libnetfilter_queue for the
allowing/denying part since we are altering the packets. The billing
depends on what page that was accessed (different sites/different
cost). Basically we already extracted the tcp, ip headers and http
packets using libnetfilter_queue. We need to parse the http headers
and put it in a struct for better analysis. However it is not that
simple as this page points out http://www.and.org/texts/server-http.
There are extra characters. Does someone know how to extract the http
headers, ie. host, accept, range, etc, efficiently. I mean, for
example, to extract the host, first get the keyword "Host: " and read/
save the characters after that. The question is until when will you
read, and what the valid characters should be there since there are
special characters. Thanks in advance!

Sonny wrote:
> Hi
> I hope this is the right group for this, or would you point me to the
> proper group for this. We are developing an application for allowing/
> denying packets and billing. We are using libnetfilter_queue for the
> allowing/denying part since we are altering the packets. The billing
> depends on what page that was accessed (different sites/different
> cost). Basically we already extracted the tcp, ip headers and http
> packets using libnetfilter_queue. We need to parse the http headers
> and put it in a struct for better analysis. However it is not that
> simple as this page points out http://www.and.org/texts/server-http.
> There are extra characters. Does someone know how to extract the http
> headers, ie. host, accept, range, etc, efficiently. I mean, for
> example, to extract the host, first get the keyword "Host: " and read/
> save the characters after that. The question is until when will you
> read, and what the valid characters should be there since there are
> special characters. Thanks in advance!
>
The HTTP spec is

<http://www.ietf.org/rfc/rfc2616.txt>

Robert