#24412: Search parameter limit always returns 400 error -----------------------------+------------------------------ Reporter: irl | Owner: metrics-team Type: defect | Status: reopened Priority: Medium | Milestone: Component: Metrics/Onionoo | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -----------------------------+------------------------------ Changes (by karsten):
* status: closed => reopened * resolution: not a bug => Comment: So, it's true that "limit" is not a valid qualified search term. Here's the relevant specification part: Qualified search terms have the form "key:value" (without double quotes) with "key" being one of the parameters listed here '''except for "search", "fingerprint", "order", "limit", "offset", and "fields",''' and "value" being the string that will internally be passed to that parameter. Regarding the stated use case, how about you simply omit the "limit" parameter and risk receiving thousands of documents back? We're in a much better position today to handle the load than we were a few years back. But let's also discuss whether we want to accept the "limit" parameter as qualified search term (and the other 5 that are currently disallowed). Basically, we'd provide two different interfaces: separate parameters and a single parameter. I see how the latter would be easier to use for applications like Relay Search. Temporarily re-opening until we're clear what we want here. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24412#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs