-
Notifications
You must be signed in to change notification settings - Fork 136
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
Fix "Invalid cookie header" warnings #343
Conversation
@sghill could you have a look at this? :-) |
@offa is it possible to add a test that verifies this behavior? MockServer or similar may be useful here |
Thanks, I'll have a look at it! |
@@ -530,7 +531,8 @@ protected CloseableHttpClient getHttpClient(PrintStream logger, Run<?, ?> run, S | |||
RequestConfig.Builder requestBuilder = RequestConfig.custom() | |||
.setSocketTimeout(timeoutInMilliseconds) | |||
.setConnectTimeout(timeoutInMilliseconds) | |||
.setConnectionRequestTimeout(timeoutInMilliseconds); | |||
.setConnectionRequestTimeout(timeoutInMilliseconds) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to usage search, the function isn't used anymore and deprecated. Thus, instead of adding tests to these changes, I can drop them. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems low risk so I think we can leave it. If there is an issue we can revert.
@sghill Test added (for the not-deprecated version; see comments above). |
@@ -530,7 +531,8 @@ protected CloseableHttpClient getHttpClient(PrintStream logger, Run<?, ?> run, S | |||
RequestConfig.Builder requestBuilder = RequestConfig.custom() | |||
.setSocketTimeout(timeoutInMilliseconds) | |||
.setConnectTimeout(timeoutInMilliseconds) | |||
.setConnectionRequestTimeout(timeoutInMilliseconds); | |||
.setConnectionRequestTimeout(timeoutInMilliseconds) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems low risk so I think we can leave it. If there is an issue we can revert.
Each status update sent to Bitbucket issues a warning in the Jenkins log:
This PR fixes the issue.
Testing done
Verified on a Jenkins instance.
Submitter checklist