Re: IE problems persist
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 58592
interpreted = N
texte = Have you tried increasing the timeout interval? http://support.microsoft.com/default.aspx?kbid=831167 This problem may occur after you apply the 832894 security update (MS04-004) or the 821814 hotfix on a computer that runs Microsoft Windows XP, Windows 2000, Windows NT 4.0, Windows Millennium Edition, or Windows 98. 821814 You receive a "page cannot be displayed" error message when you post to a site that requires authentication The 832894 security update (MS04-004) and the 821814 hotfix change how the Internet extensions for Windows (Wininet.dll) retries POST requests when a Web server resets the connection. Programs that use Windows Internet (Wininet) application programming interface (API) functions to post data (such as a user name or a password) to a Web server retry the POST request without including the POST data if the Web server closes (or resets) the initial connection request. WORKAROUND If you cannot apply the update that is discussed in the Resolution section, you can use one of the following server-side actions to work around the problem: Increase the HTTP keep-alive timeout interval on the Web server or the proxy server. There is no setting in Microsoft Internet Information Services (IIS) to control the keep-alive timeout other than the Windows registry KeepAliveTime value. But with some Web servers and some proxy servers, you can specify a connection expiration time. If you can specify a connection expiration time in the Web server or the proxy server, increase the keep-alive timeout interval. See your Web server documentation for the correct setting name and value. The default keep-alive timeout value for Internet Explorer is one minute (60 seconds). Therefore, you must use an HTTP keep-alive timeout interval on the Web server or the proxy server that is greater than one minute. For additional information about the Windows KeepAliveInterval parameter, the Windows KeepAliveTime parameter, and the Internet Explorer KeepAliveTimeout parameter, click the following article numbers to view the articles in the Microsoft Knowledge Base: 314053 TCP/IP and NBT configuration parameters for Windows XP 120642 TCP/IP and NBT configuration parameters for Windows 2000 or Windows NT 813827 How to change the default keep-alive time-out value in Internet Explorer Disable the HTTP "keep alive connections" on the server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 238210 HTTP keep-alive header sent whenever ASP buffering is enabled Salvatore D'Anna DotNetNuke Hosting V: 619-308-7606 F: 619-374-2268 http://www.DotNetNukeHosting.com -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of kalin mintchev Sent: Thursday, June 24, 2004 4:43 PM To: WebDNA Talk Subject: Re: IE problems persist well i guess i'm going to follow this thread myself -nobody else will, even sm. i called them. i wont mention names but their "tech support" is totally unexciting. after a long explaining of what the issue is i was told to send an email with the same explanation which will be then passed on to somebody else. the only mail i got back for the last 26 - 28 hours was that my email was forwarded to that somebody else. i called again and got a 3 - 4 min message that on thursdays (today) they work only until 3 pm?!? we've been using their software for 6 - 7 years now and that's the "support" we get as costumers?!? meanwhile i'm loosing a few very good clients because of that. i lost 2 when their headers weren't working - and still aren't. (they think webDNA knows what to do better than apache and gave me a suggestion to how to handle this issue their way). ok - after the vent: more tests: 1. i copied the pages causing the problem the production server to another box - bsd - that has the older webDNA 4.5 we upgraded from. that machine uses the same apache version. no problems for the IE on Win. 2. i took the webcat off the httpd conf for a few minutes on the production server - screwing up with just about 100 other websites - and tried the same form with php. no problem for the IE on Win.. now i'm sure that the problem is webDNA 6 on the production server redhat 8.0 i need help with this issue. and it ain't coming from sm apparently. can anybody suggest some places to look for a solution or leads to what the problem may be. it'd be very much appreciated.. thanks.. > hi all.. > i posted a problem here last friday... > now people can't order from the same site anymore if they use IE on windows. as i said - nothing i tried worked. restarting stuff to no avail. > i recently used different modules and builds, sent to me by Le, because of > header problems (which didn't get solved), but since then i returned to using the original module and binary. the problems started way after the switch back though. > some people suggested to upgrade to latest IE version - which i already had. the problem is on that version - any windos. > it' doesn't happened on any other browser on any platform... > i'd love some suggestions that can lead to solving this issue, please.. webCat 6; apache 1.3; redhat8.0 > and i'll cal SM too... > thanks... > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ -- Software is like sex: It's better when it's free. (Linus Torvalds) ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ __________ NOD32 1.794 (20040623) Information __________ This message was checked by NOD32 Antivirus System. http://www.nod32.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Have you tried increasing the timeout interval? http://support.microsoft.com/default.aspx?kbid=831167 This problem may occur after you apply the 832894 security update (MS04-004) or the 821814 hotfix on a computer that runs Microsoft Windows XP, Windows 2000, Windows NT 4.0, Windows Millennium Edition, or Windows 98. 821814 You receive a "page cannot be displayed" error message when you post to a site that requires authentication The 832894 security update (MS04-004) and the 821814 hotfix change how the Internet extensions for Windows (Wininet.dll) retries POST requests when a Web server resets the connection. Programs that use Windows Internet (Wininet) application programming interface (API) functions to post data (such as a user name or a password) to a Web server retry the POST request without including the POST data if the Web server closes (or resets) the initial connection request. WORKAROUND If you cannot apply the update that is discussed in the Resolution section, you can use one of the following server-side actions to work around the problem: Increase the HTTP keep-alive timeout interval on the Web server or the proxy server. There is no setting in Microsoft Internet Information Services (IIS) to control the keep-alive timeout other than the Windows registry KeepAliveTime value. But with some Web servers and some proxy servers, you can specify a connection expiration time. If you can specify a connection expiration time in the Web server or the proxy server, increase the keep-alive timeout interval. See your Web server documentation for the correct setting name and value. The default keep-alive timeout value for Internet Explorer is one minute (60 seconds). Therefore, you must use an HTTP keep-alive timeout interval on the Web server or the proxy server that is greater than one minute. For additional information about the Windows KeepAliveInterval parameter, the Windows KeepAliveTime parameter, and the Internet Explorer KeepAliveTimeout parameter, click the following article numbers to view the articles in the Microsoft Knowledge Base: 314053 TCP/IP and NBT configuration parameters for Windows XP 120642 TCP/IP and NBT configuration parameters for Windows 2000 or Windows NT 813827 How to change the default keep-alive time-out value in Internet Explorer Disable the HTTP "keep alive connections" on the server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 238210 HTTP keep-alive header sent whenever ASP buffering is enabled Salvatore D'Anna DotNetNuke Hosting V: 619-308-7606 F: 619-374-2268 http://www.DotNetNukeHosting.com -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of kalin mintchev Sent: Thursday, June 24, 2004 4:43 PM To: WebDNA Talk Subject: Re: IE problems persist well i guess i'm going to follow this thread myself -nobody else will, even sm. i called them. i wont mention names but their "tech support" is totally unexciting. after a long explaining of what the issue is i was told to send an email with the same explanation which will be then passed on to somebody else. the only mail i got back for the last 26 - 28 hours was that my email was forwarded to that somebody else. i called again and got a 3 - 4 min message that on thursdays (today) they work only until 3 pm?!? we've been using their software for 6 - 7 years now and that's the "support" we get as costumers?!? meanwhile i'm loosing a few very good clients because of that. i lost 2 when their headers weren't working - and still aren't. (they think webDNA knows what to do better than apache and gave me a suggestion to how to handle this issue their way). ok - after the vent: more tests: 1. i copied the pages causing the problem the production server to another box - bsd - that has the older webDNA 4.5 we upgraded from. that machine uses the same apache version. no problems for the IE on Win. 2. i took the webcat off the httpd conf for a few minutes on the production server - screwing up with just about 100 other websites - and tried the same form with php. no problem for the IE on Win.. now i'm sure that the problem is webDNA 6 on the production server redhat 8.0 i need help with this issue. and it ain't coming from sm apparently. can anybody suggest some places to look for a solution or leads to what the problem may be. it'd be very much appreciated.. thanks.. > hi all.. > i posted a problem here last friday... > now people can't order from the same site anymore if they use IE on windows. as i said - nothing i tried worked. restarting stuff to no avail. > i recently used different modules and builds, sent to me by Le, because of > header problems (which didn't get solved), but since then i returned to using the original module and binary. the problems started way after the switch back though. > some people suggested to upgrade to latest IE version - which i already had. the problem is on that version - any windos. > it' doesn't happened on any other browser on any platform... > i'd love some suggestions that can lead to solving this issue, please.. webCat 6; apache 1.3; redhat8.0 > and i'll cal SM too... > thanks... > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ -- Software is like sex: It's better when it's free. (Linus Torvalds) ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ __________ NOD32 1.794 (20040623) Information __________ This message was checked by NOD32 Antivirus System. http://www.nod32.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"Sal D'Anna"
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:
WebDNA-Talk Digest mode broken (1997)
PCS Frames (1997)
[WebDNA] Has anyone used 'bootstrap' as their base to create a new website? (2016)
two questions (1997)
Erotic Sites (1997)
WebTen and WebCat (1997)
[LOOP]/[BREAK] bug (2000)
newbies to web, spaces in email address (1998)
my SOS last week... (1996)
Status of variable hierarchy changes? (2000)
searching multiple databases (1997)
db could not be found or opened (2002)
multiple search commands (1997)
SMSI: closedatabase then replacefounditems inside the samesearch context ... (2002)
search form problem.. (1997)
The Box - (2003)
[protect] (2000)
RE: E-mailer error codes (1997)
Separate SSL Server (1997)
Here's how to kill a Butler Database. (1997)