Hey Darren (et al), I haven't (yet) had a chance to dig into this too deeply, but I did decode your data to take a quick peek at the atom entry:
One thing to be aware, the 400 errors you're getting are likely due to the fact that your atom entry contains neither atom threading information (indicating a reply) nor <ostatus:attention /> elements (indicating that it's a mention of the targetted user). While the latter obviously isn't required by the salmon spec, it does allow us to get (signed) confirmation that it is an intended mention. See this thread: http://groups.google.com/group/activity-streams/browse_thread/thread/8088eab30d0a5be3?hl=en (specifically http://groups.google.com/group/activity-streams/browse_thread/thread/8088eab30d0a5be3?hl=en ) We are currently throwing a 400 for atom entries without either of those. (sent to the list as we've got a few people hammering at this now) .j On Mon, Mar 8, 2010 at 9:19 PM, Darren Bounds <[email protected]> wrote: > Hi guys, > > So we're about ready to roll out our Salmon mentions endpoint and > we've been testing against Status.net, Identi.ca specifically. We've > run into a few snags that I'm hoping the Status.net team will be able > to help debug. > > 1) Mentions from Identi.ca to @[email protected] are not succeeding. We > see two WebFinger discovery requests for the appropriate user from > Idenitica/Status.net but nothing beyond that. > > 2) We consistently receive a 400 posting a mention to Identica. > Example request / response below: > > POST /main/salmon/user/46376 HTTP/1.1 > Content-Type: application/magic-envelope+xml > Content-Length: 907 > Host: identi.ca <http://identi.ca> > Connection: Keep-Alive > User-Agent: Apache-HttpClient/4.0 (java 1.5) > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?><env > xmlns="http://salmon-protocol.org/ns/magic-env";><data>PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz4KPGVudHJ5IHhtbG5zPSdodHRwOi8vd3d3LnczLm9yZy8yMDA1L0F0b20nPgogIDxpZD50YWc6Y2xpcXNldC5jb20sMjAxMDpBQUFBQUFBQUE8L2lkPiAgCiAgPGF1dGhvcj4KICAJPG5hbWU-dGVzdEBleGFtcGxlLmNvbTwvbmFtZT4KICAJPHVyaT5hY2N0OmNoYXJsaWVAY2xpcXNldC5jb208L3VyaT4KICA8L2F1dGhvcj4KICA8Y29udGVudD5IZXkgQGRhcnJlbmJvdW5kc0BpZGVudGkuY2EgU2FsbW9uIHN3aW0gdXBzdHJlYW0hPC9jb250ZW50PgogIDx0aXRsZT5IZXkgQGRhcnJlbmJvdW5kc0BpZGVudGkuY2EgU2FsbW9uIHN3aW0gdXBzdHJlYW0hPC90aXRsZT4KICA8dXBkYXRlZD4yMDEwLTAzLTA4VDIwOjA0OjAzWjwvdXBkYXRlZD4KPC9lbnRyeT4</data><encoding>base64url</encoding><alg>RSA-SHA256</alg><sig>qCYwzAfEjQ-jAdS7h8YBvcCeiMUAQJgGQanfPQVZtW-6bWoaghskcr7CONBJOtlNOiJ7xyMzOK1EWQjSVA9yBYMz8JswbESqUr7M-j8TKo7B15HVQNGVF8qX5Ob-PUwbf-Vor66BF4PapAi2n-V9MEwICiORr9UnNR1AzZxT7C8</sig></env> > > > > HTTP/1.1 400 Bad Request > Date: Tue, 09 Mar 2010 02:15:46 GMT > Server: Apache/2.2.11 (Ubuntu) PHP/5.2.6-3ubuntu4.5 with Suhosin-Patch > mod_ssl/2.2.11 OpenSSL/0.9.8g > X-Powered-By: PHP/5.2.6-3ubuntu4.5 > Vary: Accept-Encoding > Connection: close > Transfer-Encoding: chunked > Content-Type: text/html; charset=UTF-8 > > > Any assistance you can provide would be greatly appreciated. It would > be great to have both implementations talking to each other before > SXSW. > > > -- > darren bounds > [email protected] > _______________________________________________ > StatusNet-dev mailing list > [email protected] > http://lists.status.net/mailman/listinfo/statusnet-dev > -- James Walker :: http://walkah.net/ _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
