Last modified: 2012-12-30 21:12:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T39223, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37223 - Add ability to restrict number of search terms
Add ability to restrict number of search terms
Status: NEW
Product: MediaWiki
Classification: Unclassified
Search (Other open bugs)
1.20.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-30 15:58 UTC by Asher Feldman
Modified: 2012-12-30 21:12 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Asher Feldman 2012-05-30 15:58:30 UTC
Bots frequently submit huge spam documents as search queries.  In order to limit system impact, there should be a config option to set the maximum number of terms used in a search.  Terms > than that should be stripped off transparently.
Comment 1 Brion Vibber 2012-05-31 14:11:00 UTC
Number of terms (means tokenizing & determining whether operators count as terms or not?), or is just raw length of search query sufficient?
Comment 2 Asher Feldman 2012-06-02 08:35:07 UTC
I think raw query length would be a better approach, though we can set it based on the (most OR expensive OR query OR we) AND "want to" OR support.  

With this approach, perhaps it could be implemented in the core SearchEngine class so as to be agnostic to the search backend or extension used?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links