Wildcard search with leading "*" fails

[smallwheels]

Affected version

2.2.17, 2.3

May it is once more just me being stupid by I do have an issue with search. When using a wildcard like * it works flawlessly as long as it is at the end of the word. If it is at the beginning of the word there are no results. I am using the standard search on my forum (still on 2.2.17), however, this is also the case on the forums here that should run an actual version (and also Elastic search).

If i.e. I want to find postings that contain the word "fail2ban" I would expect a search for fail2ban, fail2* and *2ban to display equal results. All should find and return, among others, this recent post:

XF 2.3 Post in thread 'AI crawlers causing xf_session_activity table to reach limit'

Yesterday at 9:29 PM

Yeah the question is..... how well does the ai labyrinth work? i haven't seen anyone actually use it. I'd say it sounds like a good idea.

I don't find fail2ban is taxing on my server at all, it uses iptables to block traffic, which is the lowest level network function in linux, which is incredibly fast and it's flung off some 1000's of IP addresses big DDOS attacks on 2 core servers, amazingly.

I also filter the apache logs so they don't include css, js, png, gif, jpg, etc.. therefore my logs are 1/20th the size, reducing the amount of work fail2ban has and allowing me to set stricter...

• ebikes.com

• 

While the first two both return 9 pages of result including said post within the top three posts on the first page the third query "*2ban" returns 0 results.

Is this due to me being stupid or is it a bug?