[pubsubhubbub] Re: 0.2 core review; "as bytes" in subscription request

[Jay Rossiter]

I believe that the issue is less about binary, and more about things like "&amp;" being sent as part of the secret.     The & will be encoded per spec during transfer, and decoded by the server before being handled, because that's a protocol layer issue.  But "&amp;" should not be converted into "&", or "&apos;" into "'".   i.e. The secret should not be handled like interpreted text - simple utilized as a raw string of bytes.  It removes any ambiguity, and I think that's a Good Thing&trade;. On 10/18/2009 9:22 AM, Tim Bray wrote: On Sun, Oct 18, 2009 at 6:09 AM, Pádraic Brady <padraic.br...@yahoo.com> wrote: Presumably the secret is not a string of characters but a randomly generated stream of bytes. Bytes != Characters. Character encoding is not relevant. Sorry, my initial report was bogus, I hadn't checked http://www.w3.org/TR/1999/REC-html401-19991224/interact/forms.html#h-17.13.4 It's like this: Suppose you generate a hub.secret string and it contains the hex bytes 26 66 66 66 3D 62 61 72. Well, you can't just stick those into a application/x-www-form-urlencoded message body "as bytes" without getting a nasty surprise. You have to send them as %26%66... and so on. -T -- Jay Rossiter | Software Engineer/System Administrator Pioneering RSS Advertising Solutions jrossi...@pheedo.com | Phone: 503.896.6187 | Fax: 503.235.2216 Website: www.pheedo.com | RSS: www.pheedo.info/index.xml