davidradl commented on code in PR #58:
URL:
https://github.com/apache/flink-connector-http/pull/58#discussion_r4540947241
##########
docs/content.zh/docs/connectors/datastream/http.md:
##########
@@ -71,6 +71,14 @@ These options are specified on the builder using the
setProperty method.
| http.security.cert.client | optional | Path
to trusted certificate that should be used by connector's HTTP client for mTLS
communication.
|
| http.security.key.client | optional | Path
to trusted private key that should be used by connector's HTTP client for mTLS
communication.
|
| http.security.cert.server.allowSelfSigned | optional |
Accept untrusted certificates for TLS communication.
|
+| http.security.oidc.token.request | optional | OIDC
`Token Request` body in `application/x-www-form-urlencoded` encoding. Required
when `http.security.oidc.token.endpoint.url` is configured.
|
+| http.security.oidc.token.endpoint.url | optional | OIDC
`Token Endpoint` URL to which the token request will be issued. When set, every
sink request gets an `Authorization: Bearer <token>` header with a cached token
that is refreshed when it expires; this replaces any configured
`http.sink.header.Authorization`.
|
+| http.security.oidc.token.expiry.reduction | optional | OIDC
tokens will be requested if the current time is later than the cached token
expiry time minus this value. The default is `30s`.
|
+| http.sink.http-version | optional |
Version of HTTP to use for sink HTTP requests. Valid values are `HTTP_1_1` and
`HTTP_2`. The default is `HTTP_1_1`.
|
+| http.sink.proxy.host | optional |
Hostname of the proxy used by the sink HTTP client.
|
+| http.sink.proxy.port | optional | Port
of the proxy used by the sink HTTP client.
|
+| http.sink.proxy.username | optional |
Username used for sink proxy authentication.
|
Review Comment:
basic authentication for the userid and password?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
