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

#529 DIGEST Auth does not work if server doesn't indicate algorithm + fix in URI usage in Netty provider. #530

Merged
merged 1 commit into from Apr 9, 2014

Conversation

raulk
Copy link

@raulk raulk commented Apr 9, 2014

No description provided.

slandelle pushed a commit that referenced this pull request Apr 9, 2014
#529 DIGEST Auth does not work if server doesn't indicate algorithm + fix in URI usage in Netty provider.
@slandelle slandelle merged commit e025988 into AsyncHttpClient:1.8.x Apr 9, 2014
@slandelle slandelle added this to the 1.8.7 milestone Apr 9, 2014
@slandelle slandelle self-assigned this Apr 9, 2014
slandelle pushed a commit that referenced this pull request Apr 9, 2014
cs-workco pushed a commit to cs-workco/async-http-client that referenced this pull request Apr 13, 2023
…Client#530)

* Fix HTTP1 to HTTP2 migration while shutdown is in progress

### Motivation
Calling `HTTPClient.shutdown()` may never return if connections are still starting and one new established connection results in a state migration (i.e. from HTTP1 to HTTP2 or vice versa). We forgot to migrate the shutdown state. This could result in a large dealy until `.shutdown()` returns because we wait until connections are closed because of idle timeout. Worse, it could also never return if more requests are queued because the connections would not be idle and therefore not close itself.
###Changes
- Mirgrate shutdown state too
- add tests for this specific case

* simplify testMigrationFromHTTP1ToHTTP2WhileShuttingDown
* add http2 to http1 migration test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants