-
Notifications
You must be signed in to change notification settings - Fork 190
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
[Backport 2.x] add checks to existing unit tests #1106
base: 2.x
Are you sure you want to change the base?
Conversation
One for EndpointTest that checks for the GetRequest.id() being correctly encoded. One for PathEncodingTesst to verify that ":" is being encoded. Updated for spotless. Signed-off-by: Al Niessner <Al.Niessner@xxx.xxx> Co-authored-by: Al Niessner <Al.Niessner@xxx.xxx> (cherry picked from commit c098d8b) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@al-niessner looks like the backport failed as expected, I hear @Xtansia is looking into it, but don't hold back if you know/have/want to try a fix before him |
I am really shooting in the dark here but will give a whirl. |
@dblock @Xtansia @jordanpadams @tloubrieu-jpl I traced it down to PathEncoder and it is exactly what @Xtansia thought. I reduced the checks to:
The simplest thing to say is that Do you have a snapshot or future release that is based solely on httpClient5? I know this potentially introduces a host of new problems, but at least they will be consistent to fix. Actual errorr:
|
Oh, you know what. We can reverse the checks in PathEncoder so that if it finds httpClient5 first then use it but fail back to 4 with all of its known warts. This would essentially fix our problem because httpClient5 is in our classpath already for localhost issues. Would you be alright with such a change? |
Now I understand what you mean by 2.x prioritizing apache 4. My suggestion above is in contrast to idea. |
Backport c098d8b from #1104.