Thanks Bryan ,
I sent the floe file to a putfile and read it from there .the content looks
like below .
This portal requires browser which support
JavaScript.
Please make sure that you are using an updated browser and
Thanks.
This ties in to your answer on RecordReader etc.
There's a chance I missed it but I believe those things (e.g. nifi-api is
meant to be backwards compatible, other parts are not) are not documented
anywhere.
It'd be good to have that in my opinion.
I can put it on my todo list if others
The response shows that the content type being returned is text/html;
charset=utf-8 so that is why you can't see it in the content viewer.
You could send the flow file to a PutFile processor to write it out to
the filesystem and open it in a text editor to see what is being
returned.
If you are
Thanks Bryan for the quick response .
Below is the complete details of the response .
Attribute Values
Cache-Control
no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Connection
close
Content-Length
294
Content-Type
text/html; charset=utf-8
Date
Mon, 08 Apr 2019 11:08:25 GMT
Expires
Hello,
Can you provide more information about the response? what is the http
status code? what is the body of the response?
Can you make the same request using curl ?
-Bryan
On Mon, Apr 8, 2019 at 7:16 AM Puspak wrote:
>
> Hi team ,
> My invokehttp is making a get call over http , but the
Hi team ,
My invokehttp is making a get call over http , but the response i am getting
not able to read .
when i am reading the flow file i can only see "No viewer is registered for
this content type." I tried various option to get the json response , but
no luck.
approach i tried :
1 Accept :
