Hello Michael, Thank you for the quick reply. It seems the complete list of netstat output somehow got omitted. They have been appended to this mail. Tomcat is displayed as running on port 8080.
> HTTP 1.0 doesn't require the Host header. But I don't understand what >worked and what didn't. Clarifying this - telnet requests to / HTTP/*1.0* displayed the html of our home page. >From you comments, this would mean that had the host been provided, telnet would have printed the home page html for the request "GET / HTTP/1.1" too. We have also noted that in between some requests are successfully served by tomcat, while most of the resources are not fetched. (as explained in the previous mail) wondering what could be wrong here... Regards Sreekumar Netstat output: ------------------------------------------------------------------------------------------------------------------ - Show quoted text - TCP 192.168.103.117:3389 192.168.1.113:1432 ESTABLISHED 3844 TermService [svchost.exe] TCP 192.168.103.117:3389 192.168.1.22:1259 ESTABLISHED 3844 TermService [svchost.exe] TCP 192.168.103.117:4493 192.168.101.124:1521 ESTABLISHED 5356 [tomcat6.exe] TCP 127.0.0.1:3450 127.0.0.1:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 127.0.0.1:5152 127.0.0.1:1054 CLOSE_WAIT 2284 [jqs.exe] TCP 192.168.103.117:1790 184.84.255.35:80 <http://184.84.255.35/> CLOSE_WAIT 6008 [jucheck.exe] TCP 192.168.103.117:1973 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:2074 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:3825 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:4697 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:4701 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:4702 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:4903 72.247.219.72:80 <http://72.247.219.72/> CLOSE_WAIT 2300 [jucheck.exe] On Sat, Dec 18, 2010 at 7:58 PM, Michael Ludwig <mil...@gmx.de> wrote: > K J.Sreekumar schrieb am 18.12.2010 um 17:57 (+0530): > > (i'm adding my name before my comments so that its easier to identity > > who said what if this conversation builds up further)- > > You could configure your mail client to use standard indentation. > > > ** Sreekumar.* Using Firefox 3.6x we get the following error > > The connection was reset > > The connection to the server was reset while the page was loading. > > > ** Sreekumar.* NETSTAT was output as follows > > > > Proto Local Address Foreign Address State PID > > TCP 0.0.0.0:21 0.0.0.0:0 LISTENING > 1652 > > [inetinfo.exe] > > > > TCP 0.0.0.0:80 0.0.0.0:0 LISTENING > 1336 > > [httpd.exe] […] > > There's nothing running on port 8080. > > > - do the same from a command window on the server itself, using > "localhost" > > as the hostname. Same result ? > > > > ***Sreekumar* - The telnet output was as follows (same from local machine > > and a different workstation) > > > > HTTP/1.1 400 Bad Request > > Server: Apache-Coyote/1.1 > > Transfer-Encoding: chunked > > Date: Sat, 18 Dec 2010 09:57:04 GMT > > Connection: close > > What hostnames and ports did you use for these two telnet command? > > You're getting a Bad Request error because you omitted the Host header. > It should include the hostname, e.g. localhost: > > GET / HTTP/1.1 > Host: localhost > <CR> > <CR> > > > Connection to host lost. > > > > Next we tried with /HTTP/*1.0 *instead - In this case, when on the local > > machine/server, we did not get any response and the telnet exited > > immediately after the 2nd [ENTER]. > > > > Also, we checked telnet /HTTP/*1.1* after restarting the machine (when > > everything was running fine), it still gives a BAD REQUEST. But telnet > > requests to /HTTP/*1.0* started working. > > HTTP 1.0 doesn't require the Host header. But I don't understand what > worked and what didn't. > > -- > Michael Ludwig > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
