Bug in 'searchCols' option + a suggestion

I inspected the ajax request of table loading with serverSide set to true, and with escapeRegex set to false inside searchCols.
I found out that the request doesn't set columns[x][search][regex] in the request heder to be true, until I set regex to true as well, inside searchCols (which is not documented).
Also, in addition to (or instead of) searchCols, I would suggest an option to set search inside columns for initial filtering. I consider it as much more clear, rather than defining bunch of columns, and then defining another bunch of searchCols that match respectively, with plenty of null values in unneeded columns.