Re: tcpconnect/tcpsend problem ...
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 58230
interpreted = N
texte = I'm not at my usual computer or I'd try some this myself to be more helpful. Can you telnet to the server at port 80 for a response? One thing that sounds possible is that you're using virtual domains and the tcp connect is looking up the IP address and not sending the host needed for the server to map to the right home directory. Don't know if that's the case and I can't test where I am now. Regards, Bill -----Original Message----- From: Kenneth Grome
Sent: Mon, 7 Jun 2004 22:37:35 +0800 To: (WebDNA Talk) Subject: tcpconnect/tcpsend problem ... Here's the entire content of the page at http://incebu.com/tcplogger.html : hello The only purpose of this page is to be retrieved by a tcpconnect that's located in a template on my webdna server with this content in it: [tcpconnect host=incebu.com&port=80] [text]status=[middle startafter=987654321&endbefore=123456789][tcpsend]GET /tcplogger.html HTTP/1.0[unurl]%0D%0A%0D%0A[/unurl][/tcpsend][/middle][/text] [showif [url][status][/url]!online] [sendmail to=webdna@kengrome.com&from=server@webdna.net&subject=incebu.com is down.][status][/sendmail] [/showif] [/tcpconnect] The server is reporting a 'file not found' error when the tcpconnect tries to get the "tcplogger.html" page via the above code, but the file is there as you can see by retrieving it in a browser yourself, so the server seems to be "making a mistake" when it tries to respond to the tcpconnect request. Two other tcpconnects that look exactly like this one work fine. The only difference is that the other two tcpconnects retrieve their files from different domains on different servers -- it is only this domain (and other domains) on this server that don't seem to respond properly when I use tcpconnect. If it weren't for the fact that retrieving the file via the above link works fine, I might actually think that the file is missing. But if I can retrieve it via my browser then I think I should be able to retrieve it via tcpconnect as well. But I cannot! Has anyone else found that tcpconnect fails on a domain when the same requested page can actually be retrieved by a browser? That's the problem I'm having, and I just don't get it. If I click a browser link that gets the "tcplogger.html" page from the incebu.com server, the browser retrieves the page fine. Isn't the above tcpconnect supposed to send the same request? If so, why is the server finding and serving the page to the browser and not to the tcpconnect? Here's the actual server response I've been getting that tells me the server cannot find the "tcplogger.html" page. Maybe there's something here that someone else can see that's causing this problem, but I certainly cannot find anything. This is the entire content that's retrieved in the tcpsend, the first part is the header and the second part is the content of the Apache error page: HTTP/1.1 404 Not Found Date: Mon, 07 Jun 2004 14:00:43 GMT Server: Apache/1.3.29 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2634 mod_ssl/2.8.16 OpenSSL/0.9.7a PHP-CGI/0.1b Connection: close Content-Type: text/html; charset=iso-8859-1 404 Not Found Not Found
The requested URL /tcplogger.html was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/1.3.29 Server at www.hostingtrade.com Port 80 Of course I should be getting the content of my "tcplogger.html" page instead of the content of the error page, but I'm not -- and that's the whole problem. Please offer helpful suggestions if possible, thanks. -- Kenneth Grome WebDNA Programmer Outsource Service Provider Phone: +6332 255-6591 ------------------------------------------------------------- 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/ ------------------------------------------------------------- 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:
I'm not at my usual computer or I'd try some this myself to be more helpful. Can you telnet to the server at port 80 for a response? One thing that sounds possible is that you're using virtual domains and the tcp connect is looking up the IP address and not sending the host needed for the server to map to the right home directory. Don't know if that's the case and I can't test where I am now. Regards, Bill -----Original Message----- From: Kenneth Grome Sent: Mon, 7 Jun 2004 22:37:35 +0800 To: (WebDNA Talk) Subject: tcpconnect/tcpsend problem ... Here's the entire content of the page at http://incebu.com/tcplogger.html : hello The only purpose of this page is to be retrieved by a tcpconnect that's located in a template on my webdna server with this content in it: [tcpconnect host=incebu.com&port=80] [text]status=[middle startafter=987654321&endbefore=123456789][tcpsend]GET /tcplogger.html HTTP/1.0[unurl]%0D%0A%0D%0A[/unurl][/tcpsend][/middle][/text] [showif [url][status][/url]!online] [sendmail to=webdna@kengrome.com&from=server@webdna.net&subject=incebu.com is down.][status][/sendmail] [/showif] [/tcpconnect] The server is reporting a 'file not found' error when the tcpconnect tries to get the "tcplogger.html" page via the above code, but the file is there as you can see by retrieving it in a browser yourself, so the server seems to be "making a mistake" when it tries to respond to the tcpconnect request. Two other tcpconnects that look exactly like this one work fine. The only difference is that the other two tcpconnects retrieve their files from different domains on different servers -- it is only this domain (and other domains) on this server that don't seem to respond properly when I use tcpconnect. If it weren't for the fact that retrieving the file via the above link works fine, I might actually think that the file is missing. But if I can retrieve it via my browser then I think I should be able to retrieve it via tcpconnect as well. But I cannot! Has anyone else found that tcpconnect fails on a domain when the same requested page can actually be retrieved by a browser? That's the problem I'm having, and I just don't get it. If I click a browser link that gets the "tcplogger.html" page from the incebu.com server, the browser retrieves the page fine. Isn't the above tcpconnect supposed to send the same request? If so, why is the server finding and serving the page to the browser and not to the tcpconnect? Here's the actual server response I've been getting that tells me the server cannot find the "tcplogger.html" page. Maybe there's something here that someone else can see that's causing this problem, but I certainly cannot find anything. This is the entire content that's retrieved in the tcpsend, the first part is the header and the second part is the content of the Apache error page: HTTP/1.1 404 Not Found Date: Mon, 07 Jun 2004 14:00:43 GMT Server: Apache/1.3.29 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2634 mod_ssl/2.8.16 OpenSSL/0.9.7a PHP-CGI/0.1b Connection: close Content-Type: text/html; charset=iso-8859-1 404 Not Found Not Found
The requested URL /tcplogger.html was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/1.3.29 Server at www.hostingtrade.com Port 80 Of course I should be getting the content of my "tcplogger.html" page instead of the content of the error page, but I'm not -- and that's the whole problem. Please offer helpful suggestions if possible, thanks. -- Kenneth Grome WebDNA Programmer Outsource Service Provider Phone: +6332 255-6591 ------------------------------------------------------------- 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/ ------------------------------------------------------------- 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/
devaulw@onebox.com
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:
No one gets my client's code for free ... (2005)
& in Lookups (1997)
Emailer connect failure definitions (2003)
WebCat name recognition (1998)
Search Sort Random (2004)
Nav. 4 probs with cart - Serious problem (1997)
Searching using numbers (1998)
Mozilla/4. and Browser Info.txt (1997)
WebCatalog Use Question (1997)
shipcost (1997)
Ad Serving Software (2002)
Search group and ww (2003)
Anyone running WebMerchant 4.0? (2000)
London WebCatalog Jobs? (2000)
In Digest Dijon (2000)
Search in 2 or more catalogs (1997)
is there a global includes directory? (1998)
[WebDNA] Problem running Webdna with IIS7 (2008)
remotely add + sign (1997)
Some Questions (1997)