oh, sorry forgot to reply, the pagination bug was fixed straight away2 more bugs I found:
- Pagination in search subtitles is a bit incorrect, total_pages number is higher than the actual number of pages
Example: https://api.opensubtitles.com/api/v1/su ... id=4154796
total_pages: 8, total_count: 462, if there are 100 subs per page it should be 5 pages, not 8- Cached search results appear to be available without an api key?
For example, try to get https://api.opensubtitles.com/api/v1/su ... 796&page=2 and then try again without an api key a few times, sometimes it will give you the results
Code: Select all
{
"data": [
{
"id": "xxx",
"type": "feature",
"attributes": {....}
},
{
"id": "xxx",
"type": "feature",
...
sorry about that, the feature_type was precisely designed for this purpose, we use a dynamic serializer who can return all kind of features (movie,episode.tvshow) so type can't be set.The Endpoint /v1/features replies withThe "type" field is always "feature". I know "attributes" contains the field "feature_type" with the real type but this is inconsistent with the models.Code: Select all
{ "data": [ { "id": "xxx", "type": "feature", "attributes": {....} }, { "id": "xxx", "type": "feature", ...
It would be easier to parse if the type would be equal to the real type (Movie,TvShow or Episode).
Code: Select all
ssl.SSLError: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:645)
Users browsing this forum: No registered users and 2 guests