Skip to main content

ColdFusion 10: Disabling request timeout

A very quick post on disabling timeout for the requests. You can now set the requesttimeout to zero in cfsetting tag i.e.

<cfsetting requesttimeout=0>

This setting is particularly useful if the server is executing a task which might take longer than the usual or the response time is not known in advance.

<cfsetting requesttimeout="0"> <cfset count = 0> <cfloop condition="true"> <cfthread action="sleep" duration="1000" /> <cfoutput>#++count#</cfoutput> <cfflush> </cfloop>

The above code would run indefinitely and the request timed out page will not be shown.

Comments

  1. We were settings as something like 99999999. So why did you created this one? Who may need an endless wait? :)

    ReplyDelete
  2. Nice addition. Is there a script version as well?

    ReplyDelete
  3. Oh yes!! In cfscript you can have 'setting requestimeout=0'

    ReplyDelete
  4. setting requesttimeout to a very high value is a hack and not a clean way to disable the timeout. Some applications may need endless wait. Say your application is reading Twitter stream at regular intervals and flushes out any available data to the client.

    ReplyDelete
  5. Awesome. Is that true for all setting attributes?

    ReplyDelete
  6. In cf9, requesttimeout is not respected on a processing page containing cfthread.  Did they fix this on cf10?

    ReplyDelete
  7. Yes. setting enablecfoutputonly="true" requesttimeout="0" showdebugoutput="yes"; is supported.

    ReplyDelete
  8. @fbe7db54a197599b3d10d647b7b26a06 if you see the example provided in the post, I'm using cfthread with action ="sleep". 

    ReplyDelete
  9. Small addition: you should write requesttimeout instead of requestimeout.

    ReplyDelete
  10. This will not work in Railo though.

    ReplyDelete
  11. The title of the post clearly says 'ColdFusion 10' :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Custom validation messages for HTML5 Input elements using the constraint validation API

HTML5 has introduced several input types such as EMAIL, URL, RANGE, SEARCH, DATE, TIME, etc,. Most of the modern browsers have implemented them and are ready to be used in a HTML document. Another exciting feature introduced in HTML5 is the form validation. Instead of writing JavaScript to validate users input, browsers can now validate it and show an appropriate message if the validation fails. The validation message is shown in line with the field for which the validation has failed. The default error message is shown when the validation fails. In this post I'll explain how these error messages can be changed.

Adding beforeRender and afterRender functions to a Backbone View

I was working on a Backbone application that updated the DOM when a response was received from the server. In a Backbone View, the initialize method would perform some operations and then call the render method to update the view. This worked fine, however there was scenario where in I wanted to perform some tasks before and after rendering the view. This can be considered as firing an event before and after the function had completed its execution. I found a very simple way to do this with Underscore's wrap method.

De-obfuscating javascript code in Chrome Developer Tools

I had blogged about JavaScript debugging with Chrome Developer Tools some time back, wherein I have explained how these developer tools can help in debugging javascript code. Today Google Chrome 12 was released and my Chrome browser was updated to this version. As with every release, there have been some improvements made on performance, usability etc,. One feature that stood out for me is the ability to De-obfuscate the javascript code.

What is Minification?

Minification is the process of removing unnecessary characters such as white spaces, comments, new lines from the source code. These otherwise would be added to make the code more readable. Minifying the source code helps in reducing the file size and thereby reducing the time taken to download the file. This is the reason why most of the popular javascript libraries such as jQuery are minified. A minified jQuery file is of 31 KB in size where as an uncompressed one is about 229 KB. Unfortunately, debugging minified javascript file…