Bypassing the 100 second rule in CloudFare

[Gordon613]

I got to RabbitMQ via http://stackoverflow.com/questions/38536167/is-it-possible-to-increase-cloudflare-time-out

I have a java class that runs a report.

When the user wants to run the report, then I run the following (simplified) code

String fileName=produceReport(List parameters)

I can then display the file in the .jsp via

<iframe id="target_upload" name="target_upload" width="100%" src="<%=fileName%>" height="100%"></iframe>

Because the produceReport can take over 100 seconds to run, then the cloudfare will block it.

Is this tutorial http://www.rabbitmq.com/tutorials/tutorial-six-java.html the most pertinent for me?

(Obviously I will need to get started with the earlier tutorials but I wanted to make sure that i was not barking up the wrong tree.)

Thanks

[Michael Klishin]

Tutorial 6 demonstrates a pattern that generally assumes your client has a long lived connection.

Have you considered using Web STOMP or does Cloud Flare force the same timeout to WebSocket

connections as well? If so then I'm afraid the only reliable solution will be some kind of good ole polling

of an HTTP endpoint.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Gordon613]

Thanks. I don't know whether Cloudfare force a timeout on WebSocket Connections. I am going to check with them... 

[Gordon613]

CloudFare replied:

Websockets would create a persistent connection through Cloudflare and there's no timeout as such, but the best way of resolving this would be just to process the request in the background and respond asynchronously, and serve a 'Loading...' page or similar, rather than having the user to wait for 100 seconds. That would also give a better user experience to the user as well

[Michael Klishin]

Thank you for reporting back.

So you can try how well WebSocket connections work through Cloudflare in practice ;)

On Tue, May 23, 2017 at 6:48 PM, Gordon613 <ten...@gmail.com> wrote:

CloudFare replied:

Websockets would create a persistent connection through Cloudflare and there's no timeout as such, but the best way of resolving this would be just to process the request in the background and respond asynchronously, and serve a 'Loading...' page or similar, rather than having the user to wait for 100 seconds. That would also give a better user experience to the user as well

--

You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Gordon613]

:)

On Tuesday, May 23, 2017 at 6:51:11 PM UTC+3, Michael Klishin wrote:

Thank you for reporting back.

So you can try how well WebSocket connections work through Cloudflare in practice ;)

On Tue, May 23, 2017 at 6:48 PM, Gordon613 <ten...@gmail.com> wrote:

CloudFare replied:

Websockets would create a persistent connection through Cloudflare and there's no timeout as such, but the best way of resolving this would be just to process the request in the background and respond asynchronously, and serve a 'Loading...' page or similar, rather than having the user to wait for 100 seconds. That would also give a better user experience to the user as well

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.