[Bug] Browser extension file extension interception uses loose matching instead of strict filename extension matching #1020
Description
📝 Description
The browser extension’s file extension interception rule does not behave as a strict filename extension match.
Extension rules are expected to intercept downloads only when the final resolved filename ends with the configured extension.
However, in the current behavior, downloads may still be intercepted even when the filename does not end with the specified extension.
This is a general issue affecting extension-based interception, not limited to any single file type.
🏷️ App Version
1.8.3
💻 Platform
Windows 11
📦 Installation Type (optional)
.exe installer
⚙️ System/Device Details (optional)
No response
🔁 Steps to Reproduce
Configure interception by file extension (any extension).
Start a download whose filename does not end with that extension.
The browser download is still intercepted by AB Download Manager.
✅ Expected Behavior
Only downloads whose final filename strictly ends with the configured extension should be intercepted.
📷 Screenshots or Recordings (optional)
No response
🗒️ Additional Information (optional)
Example:
Configured extension rule: zip
Correctly intercepted:
https://example.com/files/archive.zip
Incorrectly intercepted:
Observed behavior:
The browser extension intercepts both URLs, even though the second URL does not point to a file whose name ends with .zip.
This shows that the extension rule matches zip as a path segment or token, rather than performing a strict filename extension check.
💡 Possible Solution (optional)
No response