Now HttpClient just ignores SETTINGS_MAX_CONCURRENT_STREAMS parameter, which is contained in SETTINGS frame from server side. That means whatever the server sets MAX_CONCURRENT_STREAMS, HttpClient always initiates streams rashly.

Should HttpClient support SETTINGS_MAX_CONCURRENT_STREAMS from the server?