Interface GraphQLClientConfig
public interface GraphQLClientConfig
-
Method Summary
Modifier and TypeMethodDescriptionAllowing unexpected fields in response.If true, then queries and mutations will run over the websocket transport rather than pure HTTP.headers()HTTP headers to add when communicating with the target GraphQL service.Additional payload sent on websocket initialization.Maximum number of redirects to follow.The name of the proxy configuration to use.Deprecated, for removal: This API element is subject to removal in a future version.Deprecated, for removal: This API element is subject to removal in a future version.Useproxy-configuration-nameinstead.Deprecated, for removal: This API element is subject to removal in a future version.Useproxy-configuration-nameinstead.Deprecated, for removal: This API element is subject to removal in a future version.Useproxy-configuration-nameinstead.WebSocket subprotocols that should be supported by this client for running GraphQL operations over websockets.The name of the TLS configuration (bucket) used for client authentication in the TLS registry.url()The URL location of the target GraphQL service.Maximum time in milliseconds that will be allowed to wait for the server to acknowledge a websocket connection (send a subprotocol-specific ACK message).
-
Method Details
-
url
The URL location of the target GraphQL service. -
headers
HTTP headers to add when communicating with the target GraphQL service. -
subprotocols
WebSocket subprotocols that should be supported by this client for running GraphQL operations over websockets. Allowed values are: - `graphql-ws` for the deprecated Apollo protocol - `graphql-transport-ws` for the newer GraphQL over WebSocket protocol (default value) If multiple protocols are provided, the actual protocol to be used will be subject to negotiation with the server. -
executeSingleResultOperationsOverWebsocket
If true, then queries and mutations will run over the websocket transport rather than pure HTTP. Off by default, because it has higher overhead. -
websocketInitializationTimeout
OptionalInt websocketInitializationTimeout()Maximum time in milliseconds that will be allowed to wait for the server to acknowledge a websocket connection (send a subprotocol-specific ACK message). -
proxyConfigurationName
The name of the proxy configuration to use. This setting is ignored ifproxy-hostis set. If not set and the default proxy configuration is configured (quarkus.proxy.*) then that will be used. If the proxy configuration name is set, the configuration fromquarkus.proxy.<name>.*will be used. If the proxy configuration name is set, but no proxy configuration is found with that name, then an error will be thrown at runtime. -
proxyHost
Deprecated, for removal: This API element is subject to removal in a future version.Useproxy-configuration-nameinstead.Hostname of the proxy to use. -
proxyPort
Deprecated, for removal: This API element is subject to removal in a future version.Useproxy-configuration-nameinstead.Port number of the proxy to use. -
proxyUsername
Deprecated, for removal: This API element is subject to removal in a future version.Useproxy-configuration-nameinstead.Username for the proxy to use. -
proxyPassword
Deprecated, for removal: This API element is subject to removal in a future version.Useproxy-configuration-nameinstead.Password for the proxy to use. -
maxRedirects
OptionalInt maxRedirects()Maximum number of redirects to follow. -
initPayload
Additional payload sent on websocket initialization. -
allowUnexpectedResponseFields
Allowing unexpected fields in response. If true, there will be warning log of an unexpected field. Else it throws an error. -
tlsConfigurationName
The name of the TLS configuration (bucket) used for client authentication in the TLS registry.
-
proxy-configuration-nameinstead.