mirror of
https://github.com/projectsend/projectsend.git
synced 2026-09-18 01:25:09 +00:00
ignacionelson
25b92c086b
tcp://clamav:3310djlkasjdlk connected happily. PHP reads a port the way atoi does — the digits at the front, the rest ignored — so an address with a typo on the end was saved, tested, and reported as working, while tcp://clamav:33101 went somewhere else and failed. The feedback an operator got had nothing to do with the mistake they made. ScannerAddress says what an address is: tcp:// with a host and a port of 1 to 65535 and nothing after it, or unix:// with an absolute path. It is asked in all three places an address arrives — saving, testing, and connecting. The third matters because a managed address comes from the environment and never passes the screen. The answer names the problem rather than reporting "no answer", which would be true of any unreachable scanner and would send somebody to look at their network for a typo. Checked in a browser with both addresses from the report: each is now refused on Test and on Save, with the same sentence, and tcp://clamav:3310 still comes back "Working. ClamAV 1.5.4 detected the test file".