Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force downgrading to org.apache.httpcomponents:httpclient:4.5.6 prevent URI normalization #1924

Merged
merged 5 commits into from
Aug 22, 2019

Conversation

chanseokoh
Copy link
Member

@chanseokoh chanseokoh commented Aug 21, 2019

They tracked that org.apache.httpcomponents:httpclient:4.5.7 introduced a breaking change by as part of URI normalization. There have been other reports of breakage due to the change too. Details are in googleapis/google-http-java-client#795.

I think it is safe to force this version (googleapis/google-http-java-client#795 (comment)). I verified this fixes #1914 (for Maven) and full integration tests pass.

Fixes #1914.

@chanseokoh
Copy link
Member Author

Oh, wait. Gradle doesn't seem to work this way.

@chanseokoh
Copy link
Member Author

@loosebazooka any idea to make Gradle force that particular version at plugin runtime? I tried runtime('org.apache.httpcomponents:httpclient:4.5.6') everywhere to no avail. Maven works though.

@loosebazooka
Copy link
Member

loosebazooka commented Aug 21, 2019

you might have to do it in constraints? but that might lead to some new problems in the unified build.

@loosebazooka
Copy link
Member

@chanseokoh
Copy link
Member Author

chanseokoh commented Aug 21, 2019

Still no luck. ./gradlew -q dependencies shows that every occurrence of Apache httpclient is forced to 4.5.6 (from 4.5.9) in the output, but it doesn't seem forced at plugin runtime.

@chanseokoh
Copy link
Member Author

Alright, Gradle works now. But @loosebazooka said he would look into some more safeguard.

@loosebazooka
Copy link
Member

@chanseokoh safeguard doesn't need to hold up this PR, I'll look into it though.

@chanseokoh chanseokoh requested a review from a team August 21, 2019 22:29
@chanseokoh
Copy link
Member Author

Was about to update CHANGELOG. After that, should we go for releasing 1.5.1?

@TadCordle
Copy link
Contributor

Probably

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

After upgrading to 1.5.0 I get 403 on from image retrieval
4 participants