/v2/commerce/delivery temporarily disabled
Lawton Campbell.8517:
There’s some performance issues with /v2/commerce/delivery — so I’m disabling it until those can be sorted out. Expect it to be disabled for a few weeks, unfortunately.
Risingashes.8694:
Looks like this endpoint is back up.
If intentional:
Is working (an account with a few items, which is concatenating items correctly), but:
and
(an account with over 8 million results) is resulting in:
502 – Web server received an invalid response while acting as a gateway or proxy server.
There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.
This is different from what previously happened- which was for the JSON result itself to give an error (errtimeout or similar, from memory).
Lawton Campbell.8517:
Turned it on without announce in case I had to turn it back off again.
It’s probably never going to work with those accounts, unfortunately.
Risingashes.8694:
Pagination no longer an option?
Lawton Campbell.8517:
Pagination no longer an option?
It’s on the table but I’m not sure when I’ll have time to implement it.
Risingashes.8694:
Pagination no longer an option?
It’s on the table but I’m not sure when I’ll have time to implement it.
Ah good, thought it might have been some technical limitation.
Since it affects so few people it’s hardly a priority. That being said, very much looking forward to it personally.