Missing 'X-Result-Total' response header

#1 - Sept. 9, 2014, 7:19 p.m.
Blizzard Post

Hey guys,

The API wiki says that ‘X-Result-Total’ (and ‘Count’) should be returned when querying the service using pagination.

However, they don’t seem be to be showing up. Here is the response header I get when testing with ?page=0&page_size=0


HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Server: Microsoft-IIS/7.5
X-Content-Type-Options: nosniff
Link: </v2/commerce/listings?page=1>; rel=next, </v2/commerce/listings?page=0>; rel=self, </v2/commerce/listings?page=0>; rel=first, </v2/commerce/listings?page=441>; rel=last
X-Page-Total: 442
X-Page-Size: 50
Access-Control-Allow-Origin: *
Date: Wed, 10 Sep 2014 00:13:48 GMT
Connection: close
Content-Length: 206944
#4 - Sept. 11, 2014, 1:22 p.m.
Blizzard Post

This should now be fixed!

#6 - Sept. 12, 2014, 6:45 p.m.
Blizzard Post

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?

#8 - Sept. 12, 2014, 7:02 p.m.
Blizzard Post

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.

#10 - Sept. 15, 2014, 1:40 p.m.
Blizzard Post

Fixed on dev. Don’t have an ETA on when it’ll go out to Live just yet.