Re: [WebDNA] [tcpconnect] timeout
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 112312
interpreted = N
texte = I am using server edition. Considering moving to another method (cURL) to ensure a 90 second = timeout required by payment gateway. Kind regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > On 20 May 2015, at 07:25, Donovan Brooke
wrote: >=20 > I have noticed that the default timeout on the FastCGI servers I have = worked on are shorter.=20 >=20 > There is a directive to edit that, depending on which FastCGI you are = using. >=20 > Sincerely, > Donovan >=20 >=20 >=20 > On May 19, 2015, at 4:22 PM, Stuart Tremain = wrote: >=20 >> Thanks for the info Chris >>=20 >> Shame about the SSL as that is where I am needing it. Is this = something that can/will be addressed ? >>=20 >> You mention FastCGI, but does this work with the server edition. >>=20 >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 19 May 2015, at 21:49, christophe.billiottet@webdna.us wrote: >>>=20 >>> [tcpconnect] tiemout has not been documented voluntarily; However, I = will provide some technical information here: >>>=20 >>> example: >>>=20 >>> [tcpconnect host=3Dinternic.net&port=3D43&timeout=3D60] >>> [tcpsend]XXXXXX[/tcpsend] >>> [/tcpconnect] >>>=20 >>> This will only work on Linux for the initial connect(), OSX will = keep the default timeout length when connect()ing. But after the = connection is open all operating systems will use that timeout for = read() and write() to the tcp connection. >>>=20 >>> It does *not* work for SSL connections. >>>=20 >>>=20 >>> If you want timeout longer than 30s, you will have to adjust some = FastCGI parameters too. For example, a Linux server running mod_fcgid = will need you to lengthen IOTimeout: >>>=20 >>> FcgidCmdOptions /var/www/WebDNA/WebDNA.fcgi MaxProcesses 1 = IdleTimeout 120 IOTimeout 120 >>>=20 >>> test: >>>=20 >>> After I do this it does in fact let me wait 60 seconds: >>> 18:02:24 >>> Error: couldn=92t connect to host [XX.XX.XX.XX] >>> 18:03:24 >>>=20 >>> If you don=92t do this then a 60 second connect timeout will cause = WebDNA.fcgi to be killed by mod_fcgi and you will get a 500 internal = server error. >>>=20 >>> - chris >>>=20 >>>=20 >>>=20 >>>> On May 19, 2015, at 14:25, Stuart Tremain = wrote: >>>>=20 >>>> Could this please be documented ? >>>>=20 >>>> Kind regards >>>>=20 >>>> Stuart Tremain >>>> IDFK Web Developments >>>> AUSTRALIA >>>> webdna@idfk.com.au >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
I am using server edition. Considering moving to another method (cURL) to ensure a 90 second = timeout required by payment gateway. Kind regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > On 20 May 2015, at 07:25, Donovan Brooke wrote: >=20 > I have noticed that the default timeout on the FastCGI servers I have = worked on are shorter.=20 >=20 > There is a directive to edit that, depending on which FastCGI you are = using. >=20 > Sincerely, > Donovan >=20 >=20 >=20 > On May 19, 2015, at 4:22 PM, Stuart Tremain = wrote: >=20 >> Thanks for the info Chris >>=20 >> Shame about the SSL as that is where I am needing it. Is this = something that can/will be addressed ? >>=20 >> You mention FastCGI, but does this work with the server edition. >>=20 >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 19 May 2015, at 21:49, christophe.billiottet@webdna.us wrote: >>>=20 >>> [tcpconnect] tiemout has not been documented voluntarily; However, I = will provide some technical information here: >>>=20 >>> example: >>>=20 >>> [tcpconnect host=3Dinternic.net&port=3D43&timeout=3D60] >>> [tcpsend]XXXXXX[/tcpsend] >>> [/tcpconnect] >>>=20 >>> This will only work on Linux for the initial connect(), OSX will = keep the default timeout length when connect()ing. But after the = connection is open all operating systems will use that timeout for = read() and write() to the tcp connection. >>>=20 >>> It does *not* work for SSL connections. >>>=20 >>>=20 >>> If you want timeout longer than 30s, you will have to adjust some = FastCGI parameters too. For example, a Linux server running mod_fcgid = will need you to lengthen IOTimeout: >>>=20 >>> FcgidCmdOptions /var/www/WebDNA/WebDNA.fcgi MaxProcesses 1 = IdleTimeout 120 IOTimeout 120 >>>=20 >>> test: >>>=20 >>> After I do this it does in fact let me wait 60 seconds: >>> 18:02:24 >>> Error: couldn=92t connect to host [XX.XX.XX.XX] >>> 18:03:24 >>>=20 >>> If you don=92t do this then a 60 second connect timeout will cause = WebDNA.fcgi to be killed by mod_fcgi and you will get a 500 internal = server error. >>>=20 >>> - chris >>>=20 >>>=20 >>>=20 >>>> On May 19, 2015, at 14:25, Stuart Tremain = wrote: >>>>=20 >>>> Could this please be documented ? >>>>=20 >>>> Kind regards >>>>=20 >>>> Stuart Tremain >>>> IDFK Web Developments >>>> AUSTRALIA >>>> webdna@idfk.com.au >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Stuart Tremain
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Using Plug-In while running 1.6.1 (1997)
Text data with spaces in them... (1997)
Database Helper missing? (2000)
Parameter vs. Operator (1998)
email address with spaces (2001)
Web Developer Product Awards (1997)
showif... (2000)
SHOWIF/HIDEIF empty fields (2005)
2.0 Beta (1997)
How old am I? (2004)
[if][/if] weirdness (2000)
List archive status? (1999)
[WebDNA] Two questions about sending email on Ubuntu 14.04 (2014)
# fields limited? (1997)
RE: [WebDNA] anyone successfully using webdna with paypal's NVP API? (2008)
[WebDNA] 6.2 Monitor (2012)
OT: javascript help (2003)
Can't find templaes (1997)
f2 download problems (1997)
Date problems (1997)