On 11/1/2010 4:43 PM, Brett Slatkin wrote: > X-Hub-Signature works well enough for payload-only messages, but what > about messages that have headers, like arbitrary content? I don't > think that running your own hub alleviates that problem, which is why > I'm looking for a general solution that all providers can employ. Does > that make sense?
What if the application/http mime-type was used as the content body? Would allow the headers for the content and the headers for the PuSH message to be fully seperated. I see some possible problems related to difficulty of parsing, however...
