Missing 'X-Result-Total' response header
thanks, smiley
This should now be fixed!
Still broken for me. :/ Does it take some time for API changes to roll out for everyone?
Still broken for me. :/ Does it take some time for API changes to roll out for everyone?
Looks good to me, can you provide some details?
I just checked again, and I still don’t receive the X-Result-Count or X-Result-Total headers.
Request
/v2/commerce/listings?page=1
Response headers
Content-Type: application/json; charset=utf-8
Content-Encoding: gzip
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Content-Type-Options: nosniff
Link: </v2/commerce/listings?page=0>; rel=previous, </v2/commerce/listings?page=2>; rel=next, </v2/commerce/listings?page=1>; rel=self, </v2/commerce/listings?page=0>; rel=first, </v2/commerce/listings?page=442>; rel=last
X-Page-Total: 443
X-Page-Size: 50
Access-Control-Allow-Origin: *
Date: Fri, 12 Sep 2014 23:52:07 GMT
Content-Length: 22090
Oh, hah. I totally misread that as X-Page-Total and X-Page-Size.
It’s because the commerce APIs take a different code path from the rest of the /v2 APIs. We’ll take a look at it.
Can confirm, X-Result-Count and X-Result-Total are still missing. Just in case you missed it, we are talkin about the X-Result headers, not X-Page, those are working fine now.
Edit: guess i was too slow.
Fixed on dev. Don’t have an ETA on when it’ll go out to Live just yet.