This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
The following commit(s) were added to refs/heads/main by this push:
new dbf077597 Fix #2042: http-sink and http-source say how to turn off
cookies (#3252)
dbf077597 is described below
commit dbf0775975ff8bbcaa683e3c0fef1b6c86779211
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Nov 19 10:33:43 2026 +0100
Fix #2042: http-sink and http-source say how to turn off cookies (#3252)
cookieManagementDisabled is an option of the http component, not of the
endpoint, so the Kamelets cannot take it. Their descriptions now say that
they keep and send back the cookies of the service, and that the
application property camel.component.http.cookie-management-disabled, or
camel.component.https.cookie-management-disabled for an https:// address,
turns that off.
Co-authored-by: Claude Opus 5.5 <[email protected]>
---
kamelets/http-sink.kamelet.yaml | 2 +-
kamelets/http-source.kamelet.yaml | 2 +-
.../camel-kamelets/src/main/resources/META-INF/kamelets-index.json | 4 ++--
.../camel-kamelets/src/main/resources/kamelets/http-sink.kamelet.yaml | 2 +-
.../src/main/resources/kamelets/http-source.kamelet.yaml | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/kamelets/http-sink.kamelet.yaml b/kamelets/http-sink.kamelet.yaml
index eeaab7484..779e21acd 100644
--- a/kamelets/http-sink.kamelet.yaml
+++ b/kamelets/http-sink.kamelet.yaml
@@ -39,7 +39,7 @@ spec:
Output: when it is used inside a route, the body afterwards is the
response of the service.
- Good to know: a response with a status code outside `okStatusCodeRange`,
which is `200-299` when it is not set, fails the message. The address, the
method and the proxy come only from the options; headers on the message cannot
change where it is sent. The login comes only from the options too: an
`Authorization` or `Proxy-Authorization` header on the message is removed, so a
credential that came with the message, such as the one of the caller of
`webhook-source`, is not sent on. Fo [...]
+ Good to know: a response with a status code outside `okStatusCodeRange`,
which is `200-299` when it is not set, fails the message. The address, the
method and the proxy come only from the options; headers on the message cannot
change where it is sent. The login comes only from the options too: an
`Authorization` or `Proxy-Authorization` header on the message is removed, so a
credential that came with the message, such as the one of the caller of
`webhook-source`, is not sent on. Fo [...]
required:
- url
type: object
diff --git a/kamelets/http-source.kamelet.yaml
b/kamelets/http-source.kamelet.yaml
index 3c8f05197..aff7ae86e 100644
--- a/kamelets/http-source.kamelet.yaml
+++ b/kamelets/http-source.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Output: the body is the body of the response, as bytes. The headers of
the response, such as `Content-Type`, are copied to the message, and
`CamelHttpResponseCode` holds the status code.
- Good to know: it fetches the address every `period` and sends a message
for each response, even when the data has not changed. A response with a status
code outside `okStatusCodeRange`, which is `200-299` when it is not set, sends
no message: the error is logged, and the address is fetched again at the next
period. Log in either with `authUsername` and `authPassword`, with a static
token in `authBearerToken`, or with `oauth2ClientId`, `oauth2ClientSecret` and
`oauth2TokenEndpoint`: [...]
+ Good to know: it fetches the address every `period` and sends a message
for each response, even when the data has not changed. A response with a status
code outside `okStatusCodeRange`, which is `200-299` when it is not set, sends
no message: the error is logged, and the address is fetched again at the next
period. Log in either with `authUsername` and `authPassword`, with a static
token in `authBearerToken`, or with `oauth2ClientId`, `oauth2ClientSecret` and
`oauth2TokenEndpoint`: [...]
required:
- url
type: object
diff --git
a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
index fc876d2dc..580c10f71 100644
--- a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
+++ b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
@@ -1025,7 +1025,7 @@
"supportLevel" : "Stable",
"title" : "HTTP Sink",
"summary" : "Sends each message to a web service or REST API as an HTTP or
HTTPS request, for example a POST of JSON to a webhook.",
- "description" : "Sends each message to a web service or REST API as an
HTTP or HTTPS request, for example a POST of JSON to a webhook.\n\nUse it to
push data to any service that accepts HTTP calls, such as a webhook, a REST API
or a serverless function.\n\nInput: the body is sent as the request body, as
text, bytes or a stream. Turn structured data such as a Map into JSON text
first, for example with `json-serialize-action`. The `Content-Type` header is
sent as the content type of th [...]
+ "description" : "Sends each message to a web service or REST API as an
HTTP or HTTPS request, for example a POST of JSON to a webhook.\n\nUse it to
push data to any service that accepts HTTP calls, such as a webhook, a REST API
or a serverless function.\n\nInput: the body is sent as the request body, as
text, bytes or a stream. Turn structured data such as a Map into JSON text
first, for example with `json-serialize-action`. The `Content-Type` header is
sent as the content type of th [...]
"group" : "HTTP",
"namespace" : "HTTP",
"provider" : "Apache Software Foundation"
@@ -1035,7 +1035,7 @@
"supportLevel" : "Stable",
"title" : "HTTP Source",
"summary" : "Fetches a web address with an HTTP request, a GET unless
`method` says otherwise, at a regular interval, and sends each response as a
message.",
- "description" : "Fetches a web address with an HTTP request, a GET unless
`method` says otherwise, at a regular interval, and sends each response as a
message.\n\nUse it to poll a REST API, a feed or a status page for its current
data, for example fetch the state of the orders every minute. To receive the
requests that other systems send instead, use `webhook-source`.\n\nOutput: the
body is the body of the response, as bytes. The headers of the response, such
as `Content-Type`, are c [...]
+ "description" : "Fetches a web address with an HTTP request, a GET unless
`method` says otherwise, at a regular interval, and sends each response as a
message.\n\nUse it to poll a REST API, a feed or a status page for its current
data, for example fetch the state of the orders every minute. To receive the
requests that other systems send instead, use `webhook-source`.\n\nOutput: the
body is the body of the response, as bytes. The headers of the response, such
as `Content-Type`, are c [...]
"group" : "HTTP",
"namespace" : "HTTP",
"provider" : "Apache Software Foundation"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/http-sink.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/http-sink.kamelet.yaml
index eeaab7484..779e21acd 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/http-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/http-sink.kamelet.yaml
@@ -39,7 +39,7 @@ spec:
Output: when it is used inside a route, the body afterwards is the
response of the service.
- Good to know: a response with a status code outside `okStatusCodeRange`,
which is `200-299` when it is not set, fails the message. The address, the
method and the proxy come only from the options; headers on the message cannot
change where it is sent. The login comes only from the options too: an
`Authorization` or `Proxy-Authorization` header on the message is removed, so a
credential that came with the message, such as the one of the caller of
`webhook-source`, is not sent on. Fo [...]
+ Good to know: a response with a status code outside `okStatusCodeRange`,
which is `200-299` when it is not set, fails the message. The address, the
method and the proxy come only from the options; headers on the message cannot
change where it is sent. The login comes only from the options too: an
`Authorization` or `Proxy-Authorization` header on the message is removed, so a
credential that came with the message, such as the one of the caller of
`webhook-source`, is not sent on. Fo [...]
required:
- url
type: object
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/http-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/http-source.kamelet.yaml
index 3c8f05197..aff7ae86e 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/http-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/http-source.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Output: the body is the body of the response, as bytes. The headers of
the response, such as `Content-Type`, are copied to the message, and
`CamelHttpResponseCode` holds the status code.
- Good to know: it fetches the address every `period` and sends a message
for each response, even when the data has not changed. A response with a status
code outside `okStatusCodeRange`, which is `200-299` when it is not set, sends
no message: the error is logged, and the address is fetched again at the next
period. Log in either with `authUsername` and `authPassword`, with a static
token in `authBearerToken`, or with `oauth2ClientId`, `oauth2ClientSecret` and
`oauth2TokenEndpoint`: [...]
+ Good to know: it fetches the address every `period` and sends a message
for each response, even when the data has not changed. A response with a status
code outside `okStatusCodeRange`, which is `200-299` when it is not set, sends
no message: the error is logged, and the address is fetched again at the next
period. Log in either with `authUsername` and `authPassword`, with a static
token in `authBearerToken`, or with `oauth2ClientId`, `oauth2ClientSecret` and
`oauth2TokenEndpoint`: [...]
required:
- url
type: object