W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > May 2007

Re: Raw HTTP Headers

From: Sean Owen <srowen@google.com>
Date: Fri, 25 May 2007 11:23:53 -0400
Message-ID: <e920a71c0705250823q11fa9ba8x5026c891ab526fd8@mail.gmail.com>
To: "Jo Rabin" <jrabin@mtld.mobi>
Cc: public-mobileok-checker@w3.org

On 5/25/07, Jo Rabin <jrabin@mtld.mobi> wrote:
>
>
>
> >
> > How does it modify the headers -- just trimming whitespace?
> >
> > My view on this is that we should record the entire response,
> > verbatim, in a CDATA section, Base64 encoded per EARL (or not), and
> > then feel free to embrace all kinds of normalization and parsing in
> > the moki document.
> >
> > You've got the original stashed away for the record, and then the
> > useful, parsed version in the moki document.
> >
> > So: no I'd rather not be bothered by this.
>
> I'm sorry, I don't understand, you seem to be at odds with yourself on
> this. You both don't want to do it and want to have the verbatim record?

There are two copies, no?

We have the verbatim response recorded somewhere, then, we also have
this processed version with <header> and <element> tags. I'm not
bothered if the latter is normalized in some ways, since we're already
obviously processing it quite a bit. Any question of audit trail is
answered by the verbatim copy. That seems to satisfy all requirements.
Received on Friday, 25 May 2007 15:24:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:03 GMT