Under TYPO3 10 each query creates an entry in typo3.log

[robinson2]

Example:
Mon, 12 Jul 2021 17:20:41 +0200 [WARNING] request="63475e337452e" component="TYPO3.CMS.Frontend.Controller.TypoScriptFrontendController": $TSFE->set_no_cache() was triggered. Reason: &no_cache=1 has been supplied, so caching is disabled! URL: "https://www.example.com/?type=999&no_cache=1&tx_comsolitsuggest_suggest%5Bsearch%5D=test&tx_comsolitsuggest_suggest%5Bmethod%5D=suggest". Caching is disabled!

This can be avoided by changing the following in Setup.typoscript:
plugin.tx_comsolit_suggest = USER_INT (instead of "USER")
and remove &no_cache=1 from url in page.jsFooterInline.999

[ghost]

You make the page no cache.
The change you made slow down the whole page.

[robinson2]

The get-parameter in the jsFooterInline already disabled the cache. However, this was problematic because it overflowed the log file. It is not recommended to disable the cache in production environments using no_cache. My suggestion to use USER_INT does not disable the complete cache of the page, only the plugin.
Maybe it would be better to set only the following to USER_INT:

ajaxCall {
    # ...
    100 < tt_content.list.20.comsolitsuggest_suggest
    100 = USER_INT
}

What do you think?

[kraemer-igroup]

I had the same thoughts. USER_INT should always be preferred over no_cache=1. Especially if you set disableNoCacheParameter=1 the suggestions get cached and are not working properly anymore:

I did set plugin.tx_comsolit_suggest = USER_INT. Maybe ajaxCall.100 = USER_INT is working, too.

Update: just checked it again, plugin.tx_comsolit_suggest = USER_INT still returns cached suggestions. ajaxCall.100 = USER_INT works fine.