<!-- Google Tag Manager --> <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': newDate().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-XXXXXX');</script> <!-- End Google Tag Manager --> <!-- Google Tag Manager (noscript) --> <noscript><iframesrc="//www.googletagmanager.com/ns.html?id=GTM-XXXXXX" height="0"width="0"style="display:none;visibility:hidden"></iframe></noscript> <!-- End Google Tag Manager (noscript) -->
[null,null,["最后更新时间 (UTC)：2024-04-17。"],[[["Google Tag Manager container tag uses HTTPS by default for enhanced security."],["You can switch to a protocol-relative URL (//) for flexible loading based on the page's protocol (HTTP or HTTPS)."],["Existing protocol-relative implementations of Tag Manager containers will continue to function."],["Ensure custom tags on secure pages are set up with protocol-relative or secure URLs for consistent security."]]],["Google Tag Manager uses HTTPS to load resources for security. Users can opt for protocol-relative loading by changing the container code's protocol to `//` instead of `https://`. This method ensures the container loads via HTTP or HTTPS depending on the page's protocol. Older container codes used protocol-relative URLs and remain functional. Custom tags firing on secure pages should also be protocol-relative or secure. The example codes are provided to implement this.\n"]]