Re: How to see the request header created by InvokeHTTP?

[Kevin Doran]

 Hi Luca,

Based on looking at the code here [1], I believe you need to enable
debug-level logging for this logger:

org.apache.nifi.processors.standard.InvokeHTTP

Instructions for changing log level for individual component loggers can be
found here [2]. (Ignore the part about attaching a remote debugger if you
are just interested in the logging part.)
Basically, you need to add this line to your NiFi conf/logback.xml file:



[1]
https://github.com/apache/nifi/blob/4cc20e6c0687277394f021ca1f3ececd430c5a0e/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java#L1277

[2]
https://community.cloudera.com/t5/Community-Articles/NiFi-Debugging-Tutorial/ta-p/246082


Hope this helps!
Kevin

On Mar 2, 2022 at 04:26:10, Luca Giovannini 
wrote:

>
>
> Dear All,
>
>
>
> I am having troubles replicating with InvokeHTTP (1.12.1) a call to an
> HTTP endpoint that I am successfully able to make with Postman.
>
> I use InvokeHTTP with its default values and I just add two attributes for
> ‘Authorization’ and ‘Host’.
>
>
>
> I would like to see the actual request header created by InvokeHTTP, so
> that I can compare it with the one created by Postman and try to have some
> insights on my problem from the comparison…
>
> So, how can I access the request header created by InvokeHTTP?
>
> I had a look in the nifi-app log but no detail on the call was provided.
>
>
>
> Thank you for your help!
>
>
>
> Luca
>
>
>
>
>
> *Luca Giovannini*
> Information Systems Analyst
> *Dedagroup Public Services*
>
> www.linkedin.com/in/lucagio/
>
> T +39.051.278.928 | M +39.347.799.3183 | VoIP 951.128
> Dedagroup Public Services Srl – Sede di Casalecchio di Reno, Via del
> Lavoro 67
>
> www.dedagroup.it/public-services
>
>
>
> 
>
>
> Le informazioni contenute in questo messaggio di posta elettronica sono
> riservate e confidenziali e ne e' vietata la diffusione in qualsiasi modo o
> forma. Qualora Lei non fosse la persona destinataria del presente
> messaggio, La invitiamo a non diffonderlo e ad eliminarlo, dandone
> gentilmente comunicazione al mittente.
>
> The information included in this e-mail and any attachments are
> confidential and may also be privileged. If you are not the correct
> recipient, you are kindly requested to notify the sender immediately, to
> cancel it and not to disclose the contents to any other person.
>

How to see the request header created by InvokeHTTP?

[Luca Giovannini]

Dear All,

I am having troubles replicating with InvokeHTTP (1.12.1) a call to an HTTP 
endpoint that I am successfully able to make with Postman.
I use InvokeHTTP with its default values and I just add two attributes for 
'Authorization' and 'Host'.

I would like to see the actual request header created by InvokeHTTP, so that I 
can compare it with the one created by Postman and try to have some insights on 
my problem from the comparison...
So, how can I access the request header created by InvokeHTTP?
I had a look in the nifi-app log but no detail on the call was provided.

Thank you for your help!

Luca


Luca Giovannini
Information Systems Analyst
Dedagroup Public Services
www.linkedin.com/in/lucagio/
T +39.051.278.928 | M +39.347.799.3183 | VoIP 951.128
Dedagroup Public Services Srl - Sede di Casalecchio di Reno, Via del Lavoro 67
www.dedagroup.it/public-services

[cid:image001.jpg@01D82E1C.8B4422D0]

Le informazioni contenute in questo messaggio di posta elettronica sono 
riservate e confidenziali e ne e' vietata la diffusione in qualsiasi modo o 
forma. Qualora Lei non fosse la persona destinataria del presente messaggio, La 
invitiamo a non diffonderlo e ad eliminarlo, dandone gentilmente comunicazione 
al mittente.

The information included in this e-mail and any attachments are confidential 
and may also be privileged. If you are not the correct recipient, you are 
kindly requested to notify the sender immediately, to cancel it and not to 
disclose the contents to any other person.