Special wild cards *[name], *[file] and *[path] unexpectedly match question mark

[thorstenki]

It seems that in version 3.49.2 (name of installation file is httrack_x64-3.49.2.exe), the special wild cards *[name], [file] and [path] match the question mark, in contrast to the description on https://www.httrack.com/html/filters.html.
Scenario:
Web Address in the WinHTTrack project is an URL of an HTML file which includes a link with the following file name and query string:
…/-184497018.aspx?WT.mc_n=sk_feed_faz_de
Scan Rules:
- +/184497018[name]
Result:
Unexpectedly, the file is downloaded.
For detailed description of the issue, see attachment.
Special wild cards.pdf

[xroche]

This is working as intended, so I'm closing it. The special wildcards *[name], *[file] and *[path] do not actually match the question mark. You can verify with the engine's filter self-test: *[name].html does not match foo?bar.html, *[file]end does not match foo?xend, and *[path]/end does not match a?b/end. In every case the class stops at the ?.

What you observed is a separate, deliberate feature: HTTrack tolerates a trailing query string after any otherwise-complete match, so filters are not broken by ?... suffixes. It is the same rule that makes *.aspx match page.aspx?y=2. So in +*/*184497018*[name] against /-184497018.aspx?WT.mc_n=..., the *[name] matches .aspx and the trailing ?WT.mc_n=... is tolerated by the query rule, not by the class. The class itself never crosses the ?.

This behavior is now pinned by tests in tests/01_engine-filter.test (added in #431) so it stays explicit. If you want to exclude URLs that carry a query string, put a rule on the query part, for example matching *?*.