Steps to reproduce:

1. Create a new host in a disabled state
2. Create a disabled web scenario on this disabled host
3. Enable host
4. Wait 30-60 seconds and check the HTTP server access log

Result:

172.25.0.4 - - [07/Apr/2026:03:34:31 +0000] "GET / HTTP/1.1" 200 896 "-" "Zabbix" "-"
172.25.0.4 - - [07/Apr/2026:03:35:01 +0000] "GET / HTTP/1.1" 200 896 "-" "Zabbix" "-"
172.25.0.4 - - [07/Apr/2026:03:35:31 +0000] "GET / HTTP/1.1" 200 896 "-" "Zabbix" "-"
172.25.0.4 - - [07/Apr/2026:03:36:01 +0000] "GET / HTTP/1.1" 200 896 "-" "Zabbix" "-"
172.25.0.4 - - [07/Apr/2026:03:36:31 +0000] "GET / HTTP/1.1" 200 896 "-" "Zabbix" "-"

Expected:
The disabled web scenario should not execute any HTTP requests regardless of host status changes.

Root cause:

1. dc_reschedule_httptests() in src/libs/zbxdbcache/dbconfig.c does not check httptest->status before scheduling
2. process_httptests() in src/zabbix_server/httppoller/httptest.c - the SELECT query retrieves web scenarios by httptestid but does not include a WHERE status=0 filter, so disabled scenarios that were incorrectly queued are executed