Loading Profile...
Problem with short url that leads to feedproxy.google.com
This url returned a bad result:
http://api.longurl.org/v1/expand?url=...
It reports back saying that the long url is "http://feedproxy.google.com/~r/Techcrunch/~3/k52BBJinAbA/"
If I then call the api with that url (http://api.longurl.org/v1/expand?url=...) I get back the real final url in the response (http://www.techcrunch.com/2009/04/22/...)
Something here is very odd because even in the first response I got, I got the feedproxy.google.com url but I got the real title of the page returned by the next api query (techcrunch.com).
Is longurl recursive? (it should be)
That is, if the long url is found to be another short url, will it follow that redirect and return the end result?
I hope I didn't make a mess trying to explain this issue... Let me know if I need to be clearer on something.
P.S. - Why not add feedproxy.google.com to the services list? It may not be very short... but it operates just like a shortener, and longurl already works with it correctly.
http://api.longurl.org/v1/expand?url=...
It reports back saying that the long url is "http://feedproxy.google.com/~r/Techcrunch/~3/k52BBJinAbA/"
If I then call the api with that url (http://api.longurl.org/v1/expand?url=...) I get back the real final url in the response (http://www.techcrunch.com/2009/04/22/...)
Something here is very odd because even in the first response I got, I got the feedproxy.google.com url but I got the real title of the page returned by the next api query (techcrunch.com).
Is longurl recursive? (it should be)
That is, if the long url is found to be another short url, will it follow that redirect and return the end result?
I hope I didn't make a mess trying to explain this issue... Let me know if I need to be clearer on something.
P.S. - Why not add feedproxy.google.com to the services list? It may not be very short... but it operates just like a shortener, and longurl already works with it correctly.
I’m unsure
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
Okay, this change has been pushed live. Enjoy.
The company and 1 other person say
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Yes, LongURL is recursive. The way it works now, is it checks if the "long URL" it's returning is in the list of known shortening services. If it is, it will expand it again.
The reason you're getting a bad result is because feedproxy.google.com isn't in the list of shortening services.
I originally mode it work this way to prevent, for example, a link to a Facebook message from returning the URL to the login page. I'm starting to think though, that it may be better to just follow all redirects, regardless of whether they're in the known services list or not.
Any thoughts? -
Inappropriate?Right now I am taking your services list and adding a few others to it (such as feedproxy.google.com) and then sending it to the API... And if I don't get a title... I curl it myself, following all redirects. The results seem much better this way than what the API returns... So yeah... I think that would be a great improvement.
I’m excited
-
Inappropriate?That settles it. I'll let you know when I have the change in place.
BTW, I'm planning to add an easier way for people to suggest new services for the known services list. -
-
Inappropriate?Okay, this change has been pushed live. Enjoy.
The company and 1 other person say
this solves the problem
EMPLOYEE
