Making WordPress.org

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#1005 closed defect (bug) (fixed)

Content-Disposition header not always set when downloading latest.tar.gz

Reported by: jpry's profile JPry Owned by:
Milestone: Priority: normal
Component: General Keywords:
Cc:

Description

When downloading (or just checking) the latest version of WordPress as a tar.gz file, sometimes the "Content-Disposition" header is sent, and sometimes it isn't. Here are two curl requests less than 10 seconds apart:

$ curl -I 'https://wordpress.org/latest.tar.gz'
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 29 Apr 2015 14:56:55 GMT
Content-Type: application/octet-stream
Content-Length: 6321767
Connection: keep-alive
Cache-control: private
Content-Disposition: attachment; filename=wordpress-4.2.1.tar.gz
Last-Modified: Mon, 27 Apr 2015 17:14:46 GMT
X-Frame-Options: SAMEORIGIN
X-nc: EXPIRED lax 249
Accept-Ranges: bytes
$ curl -I 'https://wordpress.org/latest.tar.gz'
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 29 Apr 2015 14:57:04 GMT
Content-Type: application/octet-stream
Content-Length: 6321767
Connection: keep-alive
Last-Modified: Mon, 27 Apr 2015 17:14:46 GMT
X-Frame-Options: SAMEORIGIN
X-nc: HIT lax 250
Accept-Ranges: bytes

The "Content-Disposition" header is useful for automatic jobs that track what the latest version of WordPress is by using this link. For that reason, it would be nice to see the header consistently sent in the response.

Change History (2)

#1 @pyhhak
9 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Thanks for the report. This bug was introduced in #1002. It should be fixed now, but let us know if you notice any other issues.

#2 @samuelsidler
9 years ago

  • Resolution changed from invalid to fixed
Note: See TracTickets for help on using tickets.