You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though http/2 is added as a dependency in the application, adding h2 in protocol-configs fails. h2 is used because it is the config-key for http/2. On the other hand, using http_1_1 to set http/1.1 config works fine.
Exception in thread "main" io.helidon.common.config.ConfigException: Unknown provider configured. Expected providers with types: [h2], but only the following providers are supported: [http_1_1], provider interface: io.helidon.webclient.spi.ProtocolConfigProvider, configured service: io.helidon.webclient.spi.ProtocolConfig
Observation
There is no Http2ProtocolConfigProvider in webclient that's why h2 does not show up as another option. Http1ProtocolConfigProvider on the other hand exists for http1 webclient
Potential Fix
Add Http2ProtocolConfigProvider.java in http2 module. Use Http1ProtocolConfigProvider.java as the template for this file and just replace all http1 related code with http2.
Add Http2ProtocolConfigProvider in module-info.java of http2 so this will be service loaded:
...
import io.helidon.webclient.http2.Http2ProtocolConfigProvider;
...
...
provides io.helidon.webclient.spi.ProtocolConfigProvider
with Http2ProtocolConfigProvider;
The text was updated successfully, but these errors were encountered:
* Fix for helidon-io#7801 - webclient proxy cannot be set using configuration.
* Fix for helidon-io#7802 - webclient protocol configuration for HTTP/2 did not work.
Environment Details
Problem Description
Even though http/2 is added as a dependency in the application, adding
h2
in protocol-configs fails.h2
is used because it is the config-key for http/2. On the other hand, using http_1_1 to set http/1.1 config works fine.Steps to reproduce
application.yaml
setting:fails with:
Observation
There is no Http2ProtocolConfigProvider in webclient that's why h2 does not show up as another option. Http1ProtocolConfigProvider on the other hand exists for http1 webclient
Potential Fix
module-info.java
of http2 so this will be service loaded:The text was updated successfully, but these errors were encountered: