Re: [WebDNA] TCP HTTP/1.1 questions
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106492
interpreted = N
texte = Thanks for the info Chris. The connection: close header certainly did the trick for losing the long timeouts. Do you have any insight how to utilize persistent connections with the dna tcp syntax? or at least the general theory of how this would flow? On 4/6/11 3:40 AM, Chris Wik wrote: > On 06.04.2011, at 05:28, Aaron Michael Kaczmarek wrote: > >> I reviewed the protocol and it seems that chunked transfer-encoding is probably the source of this problem. I don't imagine webDNA supports persistent connections, so a "Connection: Close" header must be included. I'll try this out tomorrow and let ya know what I get. > > It sounds like both ends are using KeepAlive (which is assumed to be supported by HTTP/1.1), and neither end is closing the connection until the keepalive timeout is reached. > > Connection: close in the HTTP header informs the other end that you will not be sending any further requests and wish to close the HTTP connection as soon as the request is complete. > > -- > Chris Wik > Anu Internet Services Ltd > www.cwik.ch | www.anu.net > > --------------------------------------------------------- > 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. The connection: close header certainly did the trick for losing the long timeouts. Do you have any insight how to utilize persistent connections with the dna tcp syntax? or at least the general theory of how this would flow? On 4/6/11 3:40 AM, Chris Wik wrote: > On 06.04.2011, at 05:28, Aaron Michael Kaczmarek wrote: > >> I reviewed the protocol and it seems that chunked transfer-encoding is probably the source of this problem. I don't imagine webDNA supports persistent connections, so a "Connection: Close" header must be included. I'll try this out tomorrow and let ya know what I get. > > It sounds like both ends are using KeepAlive (which is assumed to be supported by HTTP/1.1), and neither end is closing the connection until the keepalive timeout is reached. > > Connection: close in the HTTP header informs the other end that you will not be sending any further requests and wish to close the HTTP connection as soon as the request is complete. > > -- > Chris Wik > Anu Internet Services Ltd > www.cwik.ch | www.anu.net > > --------------------------------------------------------- > 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
Aaron Michael Kaczmarek
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:
Netscape for MacOS X (2001)
WebCat with WebTen (1998)
[WebDNA] [OT] Google redirect or not (2014)
Re(8): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (1998)
Anyone awake? Newby moves deeper! Sitesearch & Customer DB (2000)
Random ads (1998)
Grant, please help me ... (1997)
Setting variables. (1998)
os 8.5 (1999)
[WebDNA] WebDNA 7 (2011)
Freeze (2003)
Problems getting parameters passed into email. (1997)
Nesting format tags (1997)
JavaScript form question (2001)
Keep away (1997)
Major bug report on rootbeer (1997)
error No such file (2001)
Webcat not processed for CACHEd image error pages (1998)
[WebDNA] TLS 1.2 and [tcpconnect] (2018)
pictures / referrer etc. (1998)