Loading Profile...
I'd love to see support for ow.ly.
I'd love to see support for ow.ly
e.g. http://api.longurl.org/v1/expand?url=...
e.g. http://api.longurl.org/v1/expand?url=...
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
The best point from the company
-
Ow.ly, adjix.com, and 307.to should now be supported.
The company thinks
this is one of the best points
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Ah, yes. I will be adding support for shortening services that require an API to get the long URL shortly. Thank you for bringing this up. I hadn't realized that ow.ly used frames.
-
Inappropriate?Ow.ly, adjix.com, and 307.to should now be supported.
The company thinks
this is one of the best points
-
Inappropriate?It seems like some ow.ly urls aren't returning a title:
http://api.longurl.org/v1/expand?url=...
I’m confused
3 Comments Add a comment
This is one of the best points
-
I looked into it and that is an edge case with no easy solution. In this case usnews.com doesn't send the same headers for a HEAD request as it does for a GET request, so the *final* destination isn't returned. (If you visit the URL that API request returns you'll see there is one last redirection that takes place) The URL that is returned from a HEAD request has a content-type of application/octet-stream and therefore no title search is attempted on the document.
I hope that makes sense. -
How can you get the title from a HEAD request? Doesn't it just return the HTTP headers, which don't include the <title>?</title>
-
Sorry, I didn't include enough context in my last comment.
The way web page titles are retrieved is by first performing a HEAD request to ensure the document is in fact a web page. It is important that this first step uses a HEAD request to prevent retrieving large resources like mp3 files, exes, pdfs, etc. Once it is confirmed that the URL points to a web page a GET request is made and the <title></title> is parsed out.
In this case with this particular usnews.com URL, they don't send consistent headers between HEAD and GET requests and therefor LongURL doesn't recognize it as a web page.
I hope it isn't too big of a deal. Are you having problems with other ow.ly URLs?
EMPLOYEE
