| Summary | turba's browse property not always enforced on api searches |
| Queue | Turba |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | chuck (at) horde (dot) org |
| Requester | gb (at) atomas (dot) com |
| Created | 08/09/2007 (6538 days ago) |
| Due | |
| Updated | 08/13/2007 (6534 days ago) |
| Assigned | |
| Resolved | 08/13/2007 (6534 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Summary ⇒ turba's browse property not always enforced on api searches
State ⇒ Resolved
Queue ⇒ Turba
Version ⇒ HEAD
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ turba's browse property not enforced
Queue ⇒ IMP
State ⇒ Unconfirmed
Unfortunately, imp/contacts.php does not use this information, so it
is possible to retrieve all the addresses of a source.
The next two ones may also be related to turba. I will post them to
the turba's queue:
Also it is possible to submit a one character query. Maybe the search
should be at least 2 characters ?
Even, the search may retrieve thousands of addresses. Maybe it would
be good to limit the search to the first 500 results ? Waiting for
8000 adresses take about one minute, and put a large load on the server.