Changeset 13988

Timestamp:

08/21/2024 01:40:45 AM (8 weeks ago)

Author:

dd32

Message:

.well-known/security.txt: Bump the expiry date, and add Preferred-Languages: en.

The expiry date has been set to a dynamic date, with 6-12 months expiry (Dec 31st, or next Jun 30th, whichever is 6+ months away).
This ensures it doesn't expire, but avoids absurdly long expiries or "odd dates" (ie. today + 1 year).

Props dd32, ehtis, jorbin.

File:

• sites/trunk/wordpress.org/public_html/wp-content/mu-plugins/pub/wporg-well-known.php (modified) (1 diff)

sites/trunk/wordpress.org/public_html/wp-content/mu-plugins/pub/wporg-well-known.php

@@ -24 +24 @@
 } );
 
+/**
+ * Support for https://securitytxt.org/
+ */
 function security_txt() {
+    /*
+     * Set the expiry date to December 31st / next June 30th, whichever has 6~12 months expiry.
+     * The RFC recommends that the expiry be less than a year in the future.
+     */
+    $expires = strtotime( 'Dec 31' );
+    if ( gmdate('z') > 182 ) {
+        $expires = strtotime( 'Jun 30', $expires + WEEK_IN_SECONDS );
+    }
+
     header( 'Content-Type: text/plain')
     ?>
 Contact: https://hackerone.com/wordpress
-Expires: 2024-12-31T15:00:00.000Z
+Expires: <?php echo gmdate( 'Y-m-d', $expires ); ?>T15:00:00.000Z
 Acknowledgments: https://hackerone.com/wordpress/thanks
 Canonical: https://wordpress.org/.well-known/security.txt
 Policy: https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/
+Preferred-Languages: en
 
 # The above contact is for reporting security issues in core WordPress software itself.