Add GP-6.3.3 backcatalog reference files

reference/GlobalProtect/addressed/6.3.3-h8.html

@@ -0,0 +1,99 @@
+<table class="table colsep rowsep table-striped">
+  <!--cq:include script="../../common/tablestack.jsp" /-->
+
+  <colgroup>
+    <col style="width: 25%" />
+    <col style="width: 75%" />
+  </colgroup>
+  <thead class="thead">
+    <tr class="row">
+      <th class="entry">
+        <div class="p">Issue ID</div>
+      </th>
+      <th class="entry">
+        <div class="p">Description</div>
+      </th>
+    </tr>
+  </thead>
+
+  <tbody class="tbody">
+    <tr class="row rowsep">
+      <td class="entry">
+        <div class="p"><b class="ph b">GPC-25300</b></div>
+      </td>
+      <td class="entry relcol">
+        <div class="p">
+          Fixed an issue where GlobalProtect clients experienced frequent
+          disconnections from GlobalProtect gateways. After being disconnected,
+          users were often unable to reconnect for extended periods, and
+          connection attempts to designated gateways, including those manually
+          selected or identified as 'Best Available', would incorrectly redirect
+          to other gateways.
+        </div>
+      </td>
+    </tr>
+
+    <tr class="row rowsep">
+      <td class="entry">
+        <div class="p"><b class="ph b">GPC-25222</b></div>
+      </td>
+      <td class="entry relcol">
+        <div class="p">
+          Fixed an issue where GlobalProtect clients failed to detect captive
+          portals on public Wi-Fi networks, even when the captive portal
+          responded with an HTTP 302 Redirect. This occurred because the
+          GlobalProtect agent expected the HTTP response to be terminated by
+          `\r\n\r\n` as per RFC, but some captive portals did not adhere to
+          this, causing the agent to incorrectly report that no data was
+          received from the captive portal server and thus fail to detect the
+          portal.
+        </div>
+      </td>
+    </tr>
+
+    <tr class="row rowsep">
+      <td class="entry">
+        <div class="p"><b class="ph b">GPC-25173</b></div>
+      </td>
+      <td class="entry relcol">
+        <div class="p">
+          Fixed an issue where GlobalProtect clients on macOS devices, when
+          configured in tunnel-proxy mode, intermittently displayed an "A valid
+          PAC file is required" notification after waking up from modern
+          standby, particularly when the PAC file contained a placeholder
+          statement instead of the actual EP-FQDN.
+        </div>
+      </td>
+    </tr>
+
+    <tr class="row rowsep">
+      <td class="entry">
+        <div class="p"><b class="ph b">GPC-24992</b></div>
+      </td>
+      <td class="entry relcol">
+        <div class="p">
+          Fixed an issue where GlobalProtect users experienced significant login
+          delays after a system reboot or shutdown, such as after a weekend.
+          This delay was caused by a shared memory issue that disrupted
+          communication between the GlobalProtect agent and GlobalProtect
+          service.
+        </div>
+      </td>
+    </tr>
+
+    <tr class="row rowsep">
+      <td class="entry">
+        <div class="p"><b class="ph b">GPC-23301</b></div>
+      </td>
+      <td class="entry relcol">
+        <div class="p">
+          Fixed an issue where, when the GlobalProtect app 6.2.7 and later, was
+          installed on Windows 10 devices, the app deleted the predefined proxy
+          PAC file configuration whenever the app got disconnected regardless of
+          whether the disconnection was initiated manually or occurred
+          automatically due to a timeout.
+        </div>
+      </td>
+    </tr>
+  </tbody>
+</table>