On Fri, Jan 28, 2011 at 3:02 AM, JonM <j...@altstudio.co.uk> wrote: > The following URLs won't parse using the "tweet" button: > > "'url' parameter does not contain a valid URL." > > > http://www.pitchero.com/clubs/stockport/j/team-news-1249.html&news_id=247910
Well, that's not a valid URL. See the RFC. http://www.ietf.org/rfc/rfc1738.txt If you need a "&" right there, you'll have to encode it. > I expect this is because the string has an ampersand "&" rather than a > question mark "?" before the first GET variable. Yes. > Facebooks "share" and "like" functions both accept this formatting, as > do Google and Yahoo. My guess is that they are encoding the URL for you, and Twitter does not at this time. > Is there a reason Twitter's API does not? Is there any work around I > can use? Mainly security. We've seen people abusing the tweetbutton URLs in cross-site-scripting attempts and other forms of abuse. -j > Thanks > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
