Adjust verbosity level of Fortinet-related logging

iBecause these messages do not convey an actual error status,
use PRG_INFO instead of PRG_ERR.

Signed-off-by: Dimitri Papadopoulos <3350651-DimitriPapadopoulos@users.noreply.gitlab.com>

diff --git a/fortinet.c b/fortinet.c
index bd422c88b7ba8e8e1dd8623173371485f4caf822..f0c97a2a31abad411d83e875011febea4c889363 100644 (file)
--- a/fortinet.c
+++ b/fortinet.c
@@ -394,12 +394,12 @@ static int parse_fortinet_xml_config(struct openconnect_info *vpninfo, char *buf
                                                check_ip_src = atoi(s);
                                        if (!xmlnode_get_prop(xml_node, "tun-user-ses-timeout", &s))
                                                dropped_session_cleanup = atoi(s);
-                                       vpn_progress(vpninfo, PRG_ERR,
+                                       vpn_progress(vpninfo, PRG_INFO,
                                                     _("Server reports that reconnect-after-drop is allowed within %d seconds, %s\n"),
                                                     dropped_session_cleanup,
                                                     check_ip_src ? _("but only from the same source IP address") : _("even if source IP address changes"));
                                } else
-                                       vpn_progress(vpninfo, PRG_ERR,
+                                       vpn_progress(vpninfo, PRG_INFO,
                                                     _("Server reports that reconnect-after-drop is not allowed. OpenConnect will not\n"
                                                       "be able to reconnect if dead peer is detected. If reconnection DOES work,\n"
                                                       "please report to <openconnect-devel@lists.infradead.org>\n"));