# Decommissioning HTTP for Gradle Services

DevFeed: [Decommissioning HTTP for Gradle Services](<https://devfeed.tech/articles/decommissioning-http-for-gradle-services-24609.md>)

Original publisher: [Read original article](<https://blog.gradle.org/decommissioning-http>)

Author: Jonathan Leitschuh

Published: 2019-10-17T04:00:00Z

Content type: article

Language: en

Sources: [The Gradle Blog](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [API](<https://devfeed.tech/topics/api.md>), [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [http](<https://devfeed.tech/tags/http.md>), [java](<https://devfeed.tech/tags/java.md>), [jfrog](<https://devfeed.tech/tags/jfrog.md>)

## AI overview

Gradle announced that its services would stop accepting HTTP requests starting in January 2020. Users and organizations mirroring Gradle services, distributions, or repositories needed to update their configurations to use HTTPS. Gradle 6.0 also deprecated HTTP resource and artifact downloads in build scripts unless explicitly enabled.

## Source excerpt

Starting in January 2020, Gradle services will only serve requests made with HTTPS. From that point on, all requests made with HTTP will be denied and any builds and artifact mirrors that use a Gradle URL with the non-secure HTTP protocol will fail. If you are proxying our services through your own artifact servers like Artifactory or Nexus, you will need to ensure that you update your mirror configurations so they are using HTTPS instead of HTTP. Gradle Services This change will impact the following services. Plugin Portal By default, the Gradle build tool uses HTTPS when resolving plugins from the Plugin Portal. You should be unaffected if you do not declare a custom plugin repository. If your organization mirrors the Plugin Portal from URL plugins.gradle.org/m2/*, you should check that your mirror is using HTTPS. Gradle Distributions Since Gradle 1.2, the Gradle wrapper has used HTTPS to download Gradle distributions. You should be unaffected if your gradle-wrapper.properties uses a HTTPS URL. Gradle distributions are served from the following URLs: services.gradle.org downloads.gradle.org downloads.gradle-dn.com If your organization mirrors Gradle distributions from any of these URLs, you should check that your mirror is using HTTPS. Other Gradle software Other Gradle, Inc. produced software is published to an Artifactory repository, such as the Gradle Tooling API. Most builds do not use this repository unless they are building tooling that integrates with Gradle (like IntelliJ IDEA). The Gradle Artifactory repository is available at repo.gradle.org. Gradle Build Tool Gradle 6.0 deprecates the use of HTTP in build scripts to download resources and artifacts without an an explict opt-in. For users that require the use of HTTP, Gradle has several new APIs to continue to allow HTTP on a case-by-case basis. Timeline To ease the transition for our users, this change is coming in a few phases. When What's changing? October 29th, 2019 Gradle will begin redirecting from