Using certain params together for the cdx api causes errors.
Mixing 'limit' and 'frequency': breaks unless the limit is approximately how many snapshots should be returned given a start date and a frequency. Solution could be to find a way to regenerate limit provided a start date + frequency is generated, or add an extra layer of sorting after snapshots are received to filter out any unneeded timestamps.
Asc/desc results: currently not implemented. Need to see how it interacts with limit and if it is feasible.
Using certain params together for the cdx api causes errors.