JSON Porn

FREEMIUM
От Steppschuh | Обновлено 3 месяца назад | Entertainment
Популярность

9.4 / 10

Задержка

790ms

Уровень обслуживания

100%

Назад ко всем обсуждениям

The link to the images are broken

A
alonso.vazquez
5 лет назад

When try to retrieve info from any method, the API returns links of images, but the images are broken (it returns a 404 code error).

avatar
Steppschuh commented 5 лет назад

Forgot to update here, sorry. Everything is operational again, you should see images being available for content.

avatar
Steppschuh commented 5 лет назад

Please copy and paste the URL that you are trying to access.

A
alonso.vazquez commented 5 лет назад

I already used the image endpoint as you said, but the result is the same, this is what I get "<!DOCTYPE html>
<html>
<head>
<title>Not Found!</title>
</head>
<body>
<h1>Page not found</h1>
<p>We’re sorry, the page you are looking for is currently unavailable<br/> Please try again later</p>
</body>
</html>
"
And even If I use your end point tester, the result is the same. Do you have any idea about what might happen?

A
alonso.vazquez commented 5 лет назад

Sure, I make a request to the “porn” endpoint. Such endpoint retrieves an URL object of images if you use the “includeImages” parameter on the URL of the request, and the url image is something like this: “http://i.e.cdn.porn.com/sc/2/2941/2941327/promo/promo_8.jpg” but that image returns a 404 error code.

A
alonso.vazquez commented 5 лет назад

From your image endpoint this is the URL “https://steppschuh-json-porn-v1.p.mashape.com/image/5762431775145984/400.jpg” and from the porn endpoint i get an object array images with URLs like this one “http://i.e.cdn.porn.com/sc/2/2804/2804725/promo/promo_2.jpg” but any of those URLs return a 404.

avatar
Steppschuh commented 5 лет назад

Hey Alonso,
please let me know which exact URL you are referring to. I just checked it seems like everything is alright.

Please make sure that you are following the docs for the image endpoint. You can also click on Test Endpoint there and it will execute an actual request (which returned the requested image when I checked it).

avatar
Steppschuh commented 5 лет назад

Alright, turns out this is an issue related to the CDN of one of the sources. I’ll fix this as soon as possible and let you know once it’s resolved.

In the mean time, I’d suggest developing with older data (e.g. by adding offset=5000 to your requests).

avatar
Steppschuh commented 5 лет назад

As stated before, please use the image endpoint.

The URL that you receive is the URL where this image was originally found (the source so to say). It might not be there anymore, that’s why you should use said endpoint to request images.

A
alonso.vazquez commented 5 лет назад

Ok, thanks a lot man, I’ll be waiting for your response.

Присоединяйтесь к обсуждению – добавьте комментарий ниже:

Войдите / Зарегистрируйтесь, чтобы публиковать новые комментарии
Оценки: 3.3 - Голосов: 3