I am operating a taxi service website that allows users to book rides online, calculate fares, track driver availability, and receive booking confirmations through automated systems. Recently, we have received multiple reports from users who are running AVG Internet Security or AVG Antivirus that certain features of the website are being blocked, flagged as suspicious, or prevented from loading correctly. In some cases, the booking form does not submit successfully, while in others, fare calculation APIs fail to respond. These issues do not appear for users running other security software, which leads me to believe that AVG protection layers may be interfering with specific scripts or API calls on the site.
One of the main problems appears to involve AVG’s Web Shield or firewall components blocking AJAX requests and external API calls that are essential for real-time ride booking. The website relies on dynamic requests to calculate route distance, estimated time of arrival, and pricing based on user location input. However, some users report that after entering their pickup and drop-off details, the site freezes or displays a generic network error. When they temporarily disable AVG’s protection, the booking process works normally. I am trying to determine whether certain request headers, scripts, or endpoint patterns might be triggering false positives within AVG’s web filtering system.
Another concern involves SSL certificate validation and secure connections. The website uses HTTPS with a valid SSL certificate, but a small percentage of AVG users report security warnings or blocked connections despite the certificate being correctly configured and trusted by major browsers. This inconsistency suggests that AVG may be performing additional certificate inspection or traffic analysis that interferes with our secure connections. Understanding how AVG handles HTTPS scanning and what configurations or adjustments can prevent legitimate sites from being flagged would be extremely helpful.
Performance issues have also been noted. Some users indicate that pages load noticeably slower when AVG protection is enabled, particularly pages that include interactive maps, driver tracking elements, or payment gateways. The taxi booking system relies on multiple scripts and external resources, and it seems possible that AVG’s scanning processes may be inspecting these resources in a way that adds latency. I would appreciate advice on optimizing a website so that it works smoothly alongside AVG security products without compromising safety or functionality.
Additionally, we are concerned about maintaining compatibility with AVG’s anti-phishing and behavior detection features. Because the taxi website processes user input, payment information, and dynamic content, certain actions such as redirecting to payment gateways or generating confirmation popups may resemble suspicious behavior patterns to security software. We want to ensure that our site adheres to best practices so it is not mistakenly categorized as risky or malicious. Guidance on preventing false positives and aligning website behavior with AVG’s protection policies would be greatly appreciated.
Overall, I am seeking input from the AVG community regarding how to diagnose and resolve conflicts between AVG protection features and legitimate web applications like a taxi booking platform. Specifically, I would welcome recommendations on identifying why AVG blocks certain scripts, managing HTTPS inspection compatibility, improving performance under security scanning, and ensuring long-term reliability for users running AVG products. Any insights or troubleshooting steps would help us maintain a secure yet fully functional experience for our customers. Very sorry for long post