[wp-meta] [Making WordPress.org] #8099: Update Google fonts collection data for 6.9 release

[Making WordPress.org]

#8099: Update Google fonts collection data for 6.9 release
--------------------------------------+---------------------
 Reporter:  wildworks                 |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  General                   |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |
--------------------------------------+---------------------

Comment (by wildworks):

 @dd32

 > You should see the correct data if you were to access
 https://s.w.org/images/fonts/wp-6.9/previews/abeezee/abeezee.svg?v1 for
 example.

 I was able to access the font data correctly using a URL with GET
 parameters.


 > Can you provide the output of curl -I
 https://s.w.org/images/fonts/wp-6.9/previews/abeezee/abeezee.svg ?

 Here is the output of the command on my host machine (Windows 11):

 {{{
 D:\> curl.exe -I
 https://s.w.org/images/fonts/wp-6.9/previews/abeezee/abeezee.svg
 HTTP/1.1 200 OK
 Server: nginx
 Date: Tue, 07 Oct 2025 06:32:46 GMT
 Content-Type: image/svg+xml
 Content-Length: 3701
 Connection: keep-alive
 Last-Modified: Tue, 07 Oct 2025 00:11:42 GMT
 Vary: Accept-Encoding
 X-Frame-Options: SAMEORIGIN
 Expires: Thu, 31 Dec 2037 23:55:55 GMT
 Cache-Control: max-age=315360000
 Accept-Ranges: bytes
 Access-Control-Allow-Methods: GET, HEAD
 Access-Control-Allow-Origin: *
 Alt-Svc: h3=":443"; ma=86400
 X-nc: HIT nrt 1
 Server-Timing: a8c-cdn, dc;desc=nrt, cache;desc=HIT;dur=1.0
 X-Content-Type-Options: nosniff
 }}}

 The response appears to be correct, but when I access the same URL from a
 browser, I am still redirected to https://wordpress.org/.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8099#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org