Tickets :: [#5612] turba's browse property not always enforced on api searches

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 (6706 days ago)
Due
Updated	08/13/2007 (6702 days ago)
Assigned
Resolved	08/13/2007 (6702 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

08/13/2007 03:31:20 AM	Chuck Hagenbuch	Assigned to Chuck Hagenbuch Summary ⇒ turba's browse property not always enforced on api searches

08/13/2007 03:30:58 AM	Chuck Hagenbuch	Comment #2 State ⇒ Resolved Queue ⇒ Turba Version ⇒ HEAD	Reply to this comment
It's Turba's responsibility to enforce this, and it's been fixed in CVS.

08/09/2007 10:00:06 AM	gb (at) atomas (dot) com	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ turba's browse property not enforced Queue ⇒ IMP State ⇒ Unconfirmed	Reply to this comment
In turba's source.php, you can set some address books to NOT be browseable. 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.