Re: [WebDNA] [tcpconnect] timeout
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 112310
interpreted = N
texte = Thanks for the info Chris Shame about the SSL as that is where I am needing it. Is this something = that can/will be addressed ? You mention FastCGI, but does this work with the server edition. Kind regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > 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=E2=80=99t connect to host [XX.XX.XX.XX] > 18:03:24 >=20 > If you don=E2=80=99t 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
Associated Messages, from the most recent to the oldest:
Thanks for the info Chris Shame about the SSL as that is where I am needing it. Is this something = that can/will be addressed ? You mention FastCGI, but does this work with the server edition. Kind regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > 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=E2=80=99t connect to host [XX.XX.XX.XX] > 18:03:24 >=20 > If you don=E2=80=99t 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
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:
Kaaaaahhhhhhhnnnnnnn! (1997)
Shopping with Accounts (2003)
webcat2b12 CGI -- Date comparisons (1997)
Multiple Passwords (1997)
Webstar 1.3.1 PPC (1997)
The word TYPE in search contexts and fields (1998)
2nd WebCatalog2 Feature Request (1996)
Setting up shop (1997)
For those of you not on the WebCatalog Beta... (1997)
customizing the color of user's pages (1997)
searching with if/then (2004)
Instructions for Digest (1997)
Failed to aquire lock on database (2006)
Orders.db Update (2003)
Webcatalog 4.0 - When will we be able to beta test it? (2000)
[WriteFile] problems (1997)
WebCat cannot handle compatible search parameters? (1997)
Hosts who have upgraded to v5.0? (2003)
OT: Limit on # of Pulldown entries (1997)
why why why (2004)