Re: Signatures and Authentication information must go at end of meesage.

Panic over...

I was reading the previous version of the HTTP spec. In Roy's new draft the
chunked encoding includes a footer...!

It all now works! One caveat, signatures need to have a header indication 
pointing out that there will be a signature following... ie

WRAPPED . http/1.1
Authenticate: xxx, KEY:INBAND:24623629486
Content-Transfer-Encoding: chunked

GET foo.html HTTP/1.1
Accept: text/html

Authenticate-Footer: dskjqgw4981251i2498123==



One nit for Roy, the spec as written specifies that chunked encodings use the 
string "0" to indicate end of stream as opposed to a length of 0. The difference 
is that a conformant application could use "0000" as a length which according to 
the spec would specify a chunk _not_ end of chunks :-(

	Phill