[
https://issues.apache.org/jira/browse/NIFI-15238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-15238:
------------------------------------
Description:
The HTTP_METHOD property in InvokeHTTP should only take values GET, POST, PUT,
PATCH, DELETE, HEAD, OPTIONS or an Expression Language expression. When not
specified as an Expression Language expression, there is nothing to enforce the
value is one of GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS.
The purpose of this ticket is to add validation when the HTTP_METHOD value is
not a Expression Language expression that it is one of GET, POST, PUT, PATCH,
DELETE, HEAD or OPTIONS. If one wants to specify an arbitrary method, it should
be encased using the Expression Language literal method e.g.
{code:java}
${literal('TRACE')}{code}
to bypass the aforementioned validation.
was:
The HTTP_METHOD property in InvokeHTTP should only take values GET, POST, PUT,
PATCH, DELETE, HEAD, OPTIONS or an Expression Language expression. When not
specified as a Expression Language expression, there is nothing to enforce the
value is one of GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS.
The purpose of this ticket is to add validation when the HTTP_METHOD value is
not a Expression Language expression that it is one of GET, POST, PUT, PATCH,
DELETE, HEAD or OPTIONS. If one wants to specify an arbitrary method, it should
be encased using the Expression Language literal method e.g.
{code:java}
${literal('TRACE')}{code}
> Enforce the value for the HTTP_METHOD property in InvokeHTTP when not
> specified as an Expression Language Expression
> --------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-15238
> URL: https://issues.apache.org/jira/browse/NIFI-15238
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Daniel Stieglitz
> Assignee: Daniel Stieglitz
> Priority: Minor
>
> The HTTP_METHOD property in InvokeHTTP should only take values GET, POST,
> PUT, PATCH, DELETE, HEAD, OPTIONS or an Expression Language expression. When
> not specified as an Expression Language expression, there is nothing to
> enforce the value is one of GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS.
> The purpose of this ticket is to add validation when the HTTP_METHOD value is
> not a Expression Language expression that it is one of GET, POST, PUT, PATCH,
> DELETE, HEAD or OPTIONS. If one wants to specify an arbitrary method, it
> should be encased using the Expression Language literal method e.g.
> {code:java}
> ${literal('TRACE')}{code}
> to bypass the aforementioned validation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
