I am facing an issue with the captive portal after updating Google Chrome. I am attaching a screenshot for reference.
Help please for solving the issue.
Regards,
Ashik
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Dear Sbabu,
As per your previous email, I will follow the suggested steps. However, it is not feasible to communicate this workaround to all 300 users. Users are questioning why the issue is specific to Chrome while other browsers work fine.
If any changes require in your FortiGate firmware end please do as soon as possible.
Could you please provide a permanent solution for this Chrome-related issue at the earliest?
Thank you for your assistance.
Best regards,
Jagabandhu
+91-9439291306
As I know the whole point of portal detection (chrome uses http://www.gstatic.com/generate_204 ) introduced by modern browsers was to detect and silently redirect the users to the portal page before they try to reach a site that is using https. Redirecting an https page is not possible without using deep inspection (impossible for guests/unmanaged end users). I'm not sure why chrome choose to change this behavior but I guess it will be temporary.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1469 | |
1007 | |
748 | |
443 | |
206 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.