Title: Apache Mirroring Information Notice: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. [TOC] # Apache Mirroring Resources # {#introduction} This page describes the requirements and an ideal strategy for mirroring Apache Software Foundation [releases](release). More information can be obtained from the infrastructure@apache.org mailing list. Any project willing to use the ASF infrastructure to distribute source, binary and documentation builds must adhere to the following guidelines. These guidelines have been developed so that a consistent way to mirror our distributions can be achieved, therefore **lowering the impact of the enormous amount of bandwidth** consumed by our downloads. # Goals # {#goals} - Current ASF releases must be accessible from participating mirrors. - The mirrors should be used by default. - www.apache.org/dist/ and www.eu.apache.org/dist/ may be used only as fallback/backup mirrors. - A best-guess determination of which mirror to use should be performed. - Any system should allow the user to override the mirror selection. - All releases must be signed by the release manager. - PGP/MD5 signature links from project sites may not point to mirrors. - Only current, recommended releases should be mirrored. Old releases are automatically archived to archive.apache.org/dist/ and can be deleted from the main distribution directory. # Location of files on main server # {#location} Software distributions should not be kept on the project's website. Instead, they should be moved to the appropriate central site. There are three types of software distributions with three different locations: Current public releases: [http://www.apache.org/dist/](http://www.apache.org/dist/) : Current, official releases that have been approved by the PMC and are targetted at end-users should be placed on www.apache.org. This is the main public release site and the site that is mirrored world-wide. [minotaur.apache.org:/www/www.apache.org/dist/] Non-public releases: [http://svn.apache.org/](http://svn.apache.org/) : Releases that are not intended for general public consumption should be placed on people.apache.org. This includes automated test builds (svn.apache.org/builds/) and pre-releases aimed at the developer community, but not at end users (svn.apache.org/dist/). Essentially, any release that you do not consider *ready for prime time* should go here. [people.apache.org:/www/cvs.apache.org/] Old releases: [http://archive.apache.org/dist/](http://archive.apache.org/dist/) : Older releases that you would no longer recommend to the general public should be placed on archive.apache.org. This site automatically contains all the content of www.apache.org/dist/, but nothing is ever deleted. Therefore it should rarely be necessary to touch this site, except during a reorganization. Once a release is no longer recommended to the public, simply delete it from www.apache.org/dist/, and it will remain on archive.apache.org/dist/. [minotaur.apache.org:/www/archive.apache.org/dist/] # How can my project use mirrors? # {#use} See [here](release-download-pages) # Questions? # {#questions} If you have any questions or comments, please email the infrastructure@apache.org mailing list.