 |
The following advanced settings are common for most package types.
Field | Description |
|---|---|
Priority Resolution | Setting Priority Resolution takes precedence over the resolution order when resolving virtual repositories. Setting repositories with priority will cause metadata to be merged only from repositories set with this field. If a package is not found in those repositories, Artifactory will merge metadata from the repositories that have not been set with the Priority Resolution field. Applies to all repository types excluding Chef, CocoaPods, Debian, Git LFS, Opkg, Rust, Vagrant, and VCS repositories. For more information on package support for this feature, see the Artifactory Release Notes. |
Disable Artifact Resolution in Repository | If set, Artifactory ignores this repository when trying to resolve artifacts. The repository is also not available for download or deployment of artifacts. |
Allow Content Browsing | When set, allows Artifactory users to browse the internal contents of archives (for example, browsing specific Javadoc files from within a Javadoc archive). WarningWhen Allow Content Browsing is enabled, this functionality restricts access to authenticated users only and is not supported for trial users. This limitation applies to prevent malicious users from uploading content that may compromise security. |
Store artifacts locally | When set, Artifactory artifacts from this repository will be cached locally. If not set, direct repository-to-client streaming is used. This setting is relevant for all package types, except Ansible, Helm OCI, OCI, and Hugging Face. When might you use direct repository-to-client streaming?If your organization has multiple servers connected over a high-speed LAN, you may have one instance of Artifactory caching data on a central storage facility with additional instances of Artifactory running on other servers. In this case, it makes sense for the additional instances of Artifactory to act as satellite pass-through servers rather than have them duplicate the cached data within their own environments. |
Synchronize Properties | When set, synchronizes properties of artifacts retrieved from a remote instance of Artifactory. |
Bypass HEAD Requests | When set, Artifactory will not send a HEAD request to the remote resource before downloading an artifact for caching. NoteCocoaPods and VCS packages do not support this setting. |
Block Mismatching Mime Types | When set, artifacts will fail to download if a mismatch is detected between the requested and received MIME type, according to a list specified in the You can override this setting by adding MIME types to the override list below. NoteThis setting can be overridden by the settings of the upstream server. For example, if the upstream server allows all MIME types ( |
Enable CDN Download | Enables CDN Download requests to this repository will redirect the client to download the files directly from AWS CloudFront. Supported for Enterprise+ and Enterprise Licenses. For more information, see JFrog Cloud with CDN Distribution. NoteThe following package types do not support this setting: Go, Swift, Terraform, Alpine, Cargo, Chef, CocoaPods, Conda, Gems, Ivy, NuGet, Opkg, P2, Pub, Puppet, SBT, VCS, HuggingFace |
Disable URL Normalization | When set, prevents URL normalization from occurring. For example, a remote host that redirects to a URL containing double slash symbols as expected behavior should not change "//" to "/". |
Override Default Blocked Mime Types | The set of mime types that should override the Block Mismatching Mime Types setting. |
Propagate Query Params | When set, if query params are included in the request to Artifactory, they will be passed on to the remote repository. Generic Repositories OnlyThis setting is only available for Generic type repositories. |
Important
For information about specific settings for particular package types, see Additional Remote Repository Settings for Specific Package Types.