[WebDNA] TCP HTTP/1.1 questions

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106487
interpreted = N
texte = Greetings, I've been using APIs with WebDNA successfully with 3rd parties like Amazon and Google using the TCP syntax. However, there are a couple things nagging at me with this... note: I am making these connections via SSL and am using a Windows iis6 box with DNA6.0 I've noticed that if I make any errors constructing HTTP headers in the send (especially to a Google API), the dna page will often take several minutes to load. This mostly happens when I use HTTP/1.1 as opposed to 1.0. It seems that a well-formed 1.0 request will take several minutes to complete if I simply change it to 1.1. What's with this lag time? Does this have anything to do with "chunking"? Is there any major differences between forming 1.0 to 1.1 requests with WebDNA? Are there any particular encodings or snippets that others have successfully used? Is it important to setheaders in the page making the request? In general, does anyone have any insight why I am having problems using 1.1 rather than 1.0? Thanks! Aaron Michael Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] TCP HTTP/1.1 questions (Aaron Michael Kaczmarek 2011)
  2. Re: [WebDNA] TCP HTTP/1.1 questions (Kenneth Grome 2011)
  3. Re: [WebDNA] TCP HTTP/1.1 questions (Aaron Michael Kaczmarek 2011)
  4. Re: [WebDNA] TCP HTTP/1.1 questions (Chris Wik 2011)
  5. Re: [WebDNA] TCP HTTP/1.1 questions (Aaron Michael Kaczmarek 2011)
  6. Re: [WebDNA] TCP HTTP/1.1 questions (Kenneth Grome 2011)
  7. [WebDNA] TCP HTTP/1.1 questions (Aaron Michael Kaczmarek 2011)
Greetings, I've been using APIs with WebDNA successfully with 3rd parties like Amazon and Google using the TCP syntax. However, there are a couple things nagging at me with this... note: I am making these connections via SSL and am using a Windows iis6 box with DNA6.0 I've noticed that if I make any errors constructing HTTP headers in the send (especially to a Google API), the dna page will often take several minutes to load. This mostly happens when I use HTTP/1.1 as opposed to 1.0. It seems that a well-formed 1.0 request will take several minutes to complete if I simply change it to 1.1. What's with this lag time? Does this have anything to do with "chunking"? Is there any major differences between forming 1.0 to 1.1 requests with WebDNA? Are there any particular encodings or snippets that others have successfully used? Is it important to setheaders in the page making the request? In general, does anyone have any insight why I am having problems using 1.1 rather than 1.0? Thanks! Aaron Michael 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:

WebCat for mass emailings (1997) Revisit: speed test (2002) slightly OT: advertising schemes (2004) Separate SSL Server (1997) ConvertChars (Emailer file formats) (1998) RE: Can't get appendfile to work (1997) Nested tags count question (1997) OSX Server & WebStar5 Software 4Sale (2003) searching problem (1998) WebCat2 - Getting to the browser's username/password data (1997) off topic - dna snipets (1997) [shell]? (2000) Altavista causes a problem? (1998) [SEARCH] Context for SKU prices not working... (1998) Keep away (1997) taxrate - off by 1 cent (1997) How true is this? (1999) [WebDNA] [OT] BBEdit Glossary (2012) Bulk Processing Offline (2004) SKU lookup (1997)