Issue Summary

Possible bug in tag api call and pagenation that auto generates a wrong api call to the next page to not work. The format of the resultant API call is wrong.

Steps to Reproduce

1. First API call is like this
   https://api.bitbucket.org/2.0/repositories/XXXXX/XXXXXX/refs/tags?pagelen=100
   This will return the tags and an API call for the next page similar to
   https://api.bitbucket.org/2.0/repositories/XXXX/XXXXXX/refs/tags?pagelen=100&page=67sER
2. If you run the second API call, it will still keep you in first page, but if you switch the last part where the pagelen comes last, then you can move to page 2, like this;
   https://api.bitbucket.org/2.0/repositories/XXXXX/XXXXXXXX/refs/tags?page=67sER&pagelen=100

Expected Results

The api call that is generated from the first API call should be good to move to Page 2.

Actual Results

We need to change the API call to move to page 2.

Workaround

Workaround as mentioned above is to switch the page information and pagelen from:
pagelen=100&page=67sER
to:
page=67sER&pagelen=100