You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Marton Szasz (Jira)" <ji...@apache.org> on 2022/05/10 12:18:00 UTC
[jira] [Updated] (MINIFICPP-1828) InvokeHTTP Attributes to Send empty value means "send all", but it should mean "send none" according to docs
[ https://issues.apache.org/jira/browse/MINIFICPP-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marton Szasz updated MINIFICPP-1828:
------------------------------------
Description:
InvokeHTTP docs say that a default / empty "Attributes to Send" means no attributes are attempted to be sent as HTTP headers. But InvokeHTTP uses HTTPClient::matches which in turn uses regex_search internally, instead of regex_match. regex_search is subsequence match, but we need full sequence match.
From PROCESSORS.md: Attributes to Send Regular expression that defines which attributes to send as HTTP headers in the request. If not defined, no attributes are sent as headers.
A workaround could be adding "^$" around the text. A proper solution is to change to use regex_match.
was:
InvokeHTTP docs say that a default / empty "Attributes to Send" means no attributes are attempted to be sent as HTTP headers. But InvokeHTTP uses HTTPClient::matches which in turn uses regex_search internally, instead of regex_match. regex_search is subsequence match, but we need full sequence match.
A workaround could be adding "^$" around the text. A proper solution is to change to use regex_match.
> InvokeHTTP Attributes to Send empty value means "send all", but it should mean "send none" according to docs
> ------------------------------------------------------------------------------------------------------------
>
> Key: MINIFICPP-1828
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1828
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Marton Szasz
> Priority: Major
>
> InvokeHTTP docs say that a default / empty "Attributes to Send" means no attributes are attempted to be sent as HTTP headers. But InvokeHTTP uses HTTPClient::matches which in turn uses regex_search internally, instead of regex_match. regex_search is subsequence match, but we need full sequence match.
> From PROCESSORS.md: Attributes to Send Regular expression that defines which attributes to send as HTTP headers in the request. If not defined, no attributes are sent as headers.
> A workaround could be adding "^$" around the text. A proper solution is to change to use regex_match.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)