Knowledge base/Feature Requests
PlannedDoneNot planned
multi-gets shouldn't fail on invalid URL
Philippe
suggested this on September 03, 2010 14:36
Currently, if any of the URLs in a multi-get request are malformed, the entire request will fail with an HTTP error 400: Bad Request. It would be much more useful if it still returned useful results for the valid URLs and and a type:error for the broken ones.
Thanks!
Comments
Any update on this? It prevents me from using multi-get. In case I wasn't clear, here's an example:
http://api.embed.ly/v1/api/oembed?urls=http://imgur.com/c7pJa,http:...
This query will return an array of three OEmbed object, with the last one being an error object.
However, the following query, in which the last URL is malformed, will cause embedly to return an HTTP 400 error.
http://api.embed.ly/v1/api/oembed?urls=http://imgur.com/c7pJa,http:...,htp://imgur.com/NwB5WELLL
I'd rather not have my whole query fail in the event that a user enters an invalid URL, so I'm still stuck using single queries for each URL.
But apart from that problem, I have to say that embedly is truly fantastic! It saves me from writing and maintaining countless page scrapers.
This has been updated, multi-gets should not fail a whole request. For quicker support or any other issues please submit a ticket.