Disable "content:" searches
Disable "content:" searches
Is there a way to disable "content:" ?
Each time a user finds out about it they try to use it (via HTTP), only for the server to spin lots of CPU usage and I/O for a long time, searching millions of files. I'd like to avoid that if possible.
If not, it could be a new option under General->Search: "Allow content search".
Thanks!
Each time a user finds out about it they try to use it (via HTTP), only for the server to spin lots of CPU usage and I/O for a long time, searching millions of files. I'd like to avoid that if possible.
If not, it could be a new option under General->Search: "Allow content search".
Thanks!
Re: Disable "content:" searches
I'm afraid, when I'm not thinking, I've fallen for this myself.
More than once. :0)
More than once. :0)
Re: Disable "content:" searches
How can one type the long word content: by accident ?
You can define a macro named content which just searches some named short document
or only a certain dir.
You can define a macro named content which just searches some named short document
or only a certain dir.
Re: Disable "content:" searches
Thanks, that works!
Re: Disable "content:" searches
.. when running Everything 1.5.
(On 1.4, the created content: macro is valid in the Everything search bar, but when using the http server, the original content: function prevails) EDIT: Poor choice of words; I should have said that the self-defined macro is not available in the http server.
Re: Disable "content:" searches
Ah, drat. I had only tested on the GUI app.
I'm not ready to upgrade to 1.5 yet, but it can wait.
I'm not ready to upgrade to 1.5 yet, but it can wait.
Re: Disable "content:" searches
I have added to my TODO list: add an option to prevent reading file content.
Thank you for the suggestion.
Thank you for the suggestion.
Re: Disable "content:" searches
Thank you!
Reading on the new content indexing options of v1.5:
So the notindexed: may also need to be disabled. Then we can just set it to index files of type "*.nosuchthing".
Some related options you might want to consider:
- allow content search only on specific filetypes (distinct from indexed file types)
- allow content search only on files smaller than X KB
- do content search only on the first X KB of each file
- stop content search after a given timeout, present only results found so far (this could apply to other complex/long queries as well - perhaps a timeout:10s modifier?)
As for me, I only need the option to fully disable it.
Reading on the new content indexing options of v1.5:
Code: Select all
When index content is enabled, content: will only search files included by your index content settings.
To search for text in files that are not included by your index content settings, use the notindexed: search modifier.
Some related options you might want to consider:
- allow content search only on specific filetypes (distinct from indexed file types)
- allow content search only on files smaller than X KB
- do content search only on the first X KB of each file
- stop content search after a given timeout, present only results found so far (this could apply to other complex/long queries as well - perhaps a timeout:10s modifier?)
As for me, I only need the option to fully disable it.
Re: Disable "content:" searches
Thats already possible.
Please try to look at least once in the Options / Content before using or complaining.
Re: Disable "content:" searches
I'm not complaining about anything.
Also, I disagree. The current options for the v1.5 "content" are for the new in-memory content index feature. What I'm talking about is the previous "content:" modifier, which is now "notindexed:content:". For that, there are no filetype/filesize filters, AFAIK. It's not clear if the new "content" options also apply to notindexed: searches, but logic says they don't.
I mean, it's right there in the text you quoted... "(distinct from indexed file types)".
Also, I disagree. The current options for the v1.5 "content" are for the new in-memory content index feature. What I'm talking about is the previous "content:" modifier, which is now "notindexed:content:". For that, there are no filetype/filesize filters, AFAIK. It's not clear if the new "content" options also apply to notindexed: searches, but logic says they don't.
I mean, it's right there in the text you quoted... "(distinct from indexed file types)".
Re: Disable "content:" searches
I guess you will not use notindexed: anyway
so you have full control whats indexed if you are using content:
so you have full control whats indexed if you are using content:
Re: Disable "content:" searches
Thanks, that option would be great...that will stop me accidentally indexing when my brain isn't in gear.
Re: Disable "content:" searches
As I said on the first post, it's not about me - it's users trying out stuff on the Everything WebServer after they RTFM. Which, surprisingly, they do once in a while. Not funny with 130TB of data.
Re: Disable "content:" searches
I have put on my TODO list to only search indexed information with the HTTP server. (with an option to disable)
Thank you for the suggestions.
Thank you for the suggestions.
Re: Disable "content:" searches
Everything 1.5.0.1278a will now block search functions that access disk from the HTTP server.
In other words, Everything will now only access indexed information from the HTTP server.
To allow disk access from the HTTP Server:
In other words, Everything will now only access indexed information from the HTTP server.
To allow disk access from the HTTP Server:
- In Everything 1.5, from the File menu, click Exit.
- Open your %APPDATA%\Everything\Plugins.ini
- Under the [HTTP Server.dll] section.
- Change the following line:
allow_disk_access=0
to:
allow_disk_access=1 - Save changes and exit Notepad.
- Restart Everything.
Re: Disable "content:" searches
I can't find this line in the ini file....
Last edited by harryray2 on Thu Sep 30, 2021 3:40 pm, edited 1 time in total.