Swatantra-66 commented on PR #191:
URL: https://github.com/apache/nuttx-website/pull/191#issuecomment-5984206383

   Hi @cederom!
   
   Here is the difference between them and why `closer.lua` with 
`?action=download` is the ASF-recommended standard:
   
   1. **`downloads.apache.org`** is the master ASF origin server. It hosts the 
source of truth for current releases, KEYS, signatures (`.asc`), and hashes 
(`.sha512`). However, [ASF Infra 
guidelines](https://infra.apache.org/release-download-pages.html#closer) 
explicitly state that release tarballs should not be served directly to the 
public from `downloads.apache.org` to protect the origin server's bandwidth (it 
does not redirect to CDN; it serves the full ~140MB file directly).
   
   2. **`dlcdn.apache.org`** is the global CDN (backed by Varnish/Fastly edge 
caches), which caches active release tarballs for fast global distribution. 
However, `dlcdn` only keeps current active releases (older archived releases 
get removed).
   
   3. **`closer.lua` with `?action=download`** gives the best of both worlds:
      - For **current releases** (like 13.1.0), it issues an immediate `HTTP 
302` redirect directly to `dlcdn.apache.org` without rendering the HTML mirror 
page.
      - For **older/incubator releases** (like 10.0.1 or 9.1.1), it 
automatically issues an `HTTP 302` redirect to `archive.apache.org`.
      - It complies 100% with the official [ASF Release Download 
Policy](https://infra.apache.org/release-download-pages.html#closer), which 
mandates projects use the `closer.lua` dispatcher for release downloads.
   
   So `closer.lua?...?action=download` ensures users get direct one-click 
downloads via `dlcdn`, while staying fully compliant with ASF infra rules and 
keeping older release links working!
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to