Re: InvokeHTTP vs invalid SSL certificates

Just import the certificate into the trust store. > On 4. Mar 2022, at 13:59, Jean-Sebastien Vachon > wrote: > > Hi all, > > what is the best way to deal with invalid SSL certificates when trying to > open an URL using InvokeHTTP? > > > Thanks > > Jean-Sébastien Vachon > Co-Founder &

Re: InvokeHTTP vs invalid SSL certificates

If it wasn't already clear, the majority of SSL certificates should be signed by the certificate authorities in Java's default cacerts truststore or potentially you could find another public truststore (firefox's for example) that would contain the root certificate authorities for most of the

Re: InvokeHTTP vs invalid SSL certificates

You can set up a SSLManager to ignore all errors , but it is not safe. Other option maybe put a reverse proxy in the middle

Re: InvokeHTTP vs invalid SSL certificates

Thanks David for the information. My main issue is that we are doing massive web scraping (over 400k websites and growing) and I can not just add each certificate manually. I can probably automate most of it but I wanted to see what options were available to me. Thanks again. I will look into

Re: InvokeHTTP vs invalid SSL certificates

Thanks for raising this question. The InvokeHTTP processor relies on the OkHttp client library, which implements standard TLS handshaking and hostname verification as described in their documentation: https://square.github.io/okhttp/features/https/ There are many things that could make a

InvokeHTTP vs invalid SSL certificates

Hi all, what is the best way to deal with invalid SSL certificates when trying to open an URL using InvokeHTTP? Thanks Jean-Sébastien Vachon Co-Founder & Architect Brizo Data, Inc. www.brizodata.com

Re: InvokeHTTP performance - max out at 50 post per sec.

Hi Isha Thanks for your reply. I have tried to play with the scheduling, and it doesn't help much. So I will use the concurrent task. Had hoped there where other things which could be tweaked to get it to run faster. kind regards Jens M. Kofoed Den fre. 4. mar. 2022 kl. 10.16 skrev Isha Lamboo

RE: InvokeHTTP performance - max out at 50 post per sec.

Hi Jens, The behaviour you describe doesn’t seem abnormal if the round-trip time for a request is around 20ms in you test setup. A single InvokeHTTP would process requests one by one and that gives 1000 ms /20 ms = 50 requests per second. Increasing concurrent tasks to send requests in

InvokeHTTP performance - max out at 50 post per sec.

Hi I have created some small test with invokeHTTP, and it seems like that invokeHTTP only can handle 50 flowfiles per second. If I configure the invokeHTTP to have x Concurrent Tasks, the output increase with x times. I created a very small flow GenerateFlowFile File Size: 100kb Batch size: