Apache HttpClient failed to download yarn package from s3.amazonaws.com (redirection from github) #138
Comments
|
Hi @huynguyentuong, At the moment, I didn't succeed in reproducing the issue. Either locally with my Windows workstation, or with automated tests under Travis (Windows Server, Mac OS and Linux), everything works fine.
I have no idea how to fix the issue now, and I don't want to disable any SSL verification when the plugin uses the Apache HTTP client, for security reasons of course.
Finally:
Thank you very much for your help! |
|
Hi @huynguyentuong, After some research, I don't see any reason the plugin and its internal Apache HTTP client would fail with the However, I may have made a mistake in the plugin, by using version 4.5.13 of the Apache HTTP client. The client latest version is 5.0.3, and works also perfectly. There's no reason the plugin does not use the latest version. It will be upgraded in the next release. My question is still pending: do you still face this issue, or was it temporary? |
|
Hi @v1nc3n4, Thank you very much for looking into this. I tried to run the test and it is green. The result is as following The issue is still there, but let me investigate more, or try to upgrade to Apache HTTP 5.xx to see whether it works or not |
|
Hi @v1nc3n4, I think I found the issue, probably because of library version clashing of plugins, one of the other plugins I used must be also having another version of Apache HTTP client that having the SSL bug. If I create a completely empty Gradle project with only our frontend plugin here then we have no problem. Let me investigate more to see which plugin is that and work with the author to solve it and put the workaround here. Thanks again for your help. Cheers, |
|
I found a workaround, just explicitly specify the version of HTTP client as following buildscript {
repositories {
jcenter()
}
dependencies {
classpath("org.apache.httpcomponents:httpclient:4.5.13")
}
} |
|
Hello, I’m glad you also found a workaround by explicitly setting the dependency in the project. I’m sure it will help a lot in the future because it’s not the first time a dependency issue occurs with another library. Cảm ơn nhiều anh giúp em, chúc anh ngày ngon! |
|
"I don't see any reason the plugin and its internal Apache HTTP client would fail with the s3.amazonaws.com domain name." |
|
Hi @seleznevmm Actually, the issue you faced is a different issue, and it is a relevant behaviour I guess. The AWS S3 server uses a wildcard SSL certificate Hope this helps! |
|
I'm seeing the same issue. Adding the classpath dependency didn't fix it. Anything else I can try? I also tried with |
|
Hi @efenderbosch, Have you tried running the Regards |
|
@efenderbosch |
|
It works as expected in an empty project. |
|
@efenderbosch, |
|
First thing I tried was 4.5.13.
|
|
Sorry to read that. Apart from progressing step by step by adding dependencies into a sample project and see when the problem occurs, I don't have a solution. To me, it doesn't seem to be a plugin issue. |
|
The only version of |
Hi,
Description
What I am trying to do:
./gradlew installYarnExpected results: yarn is installed
Actual results:
Environment
Settings in
build.gradle.ktsfile:frontend { nodeVersion.set("14.15.0") nodeInstallDirectory.set(file("${buildDir}/node")) assembleScript.set("run build") yarnEnabled.set(true) yarnVersion.set("1.22.5") }Investigation
Seems like Apache HttpClient failed to do SSL hostname validation for the file. I don't have Windows or Linux to test so not sure whether it works in those environments or not.
The text was updated successfully, but these errors were encountered: