DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7286>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7286 Tomcat addresses initially cannot be resolved without path Summary: Tomcat addresses initially cannot be resolved without path Product: Tomcat 4 Version: Unknown Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: Minor Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I installed the JWSDP 1.0 ea1 on a mandrake machine. When typing http://hostname:8080 from a Windows box on the LAN it gives an error "No Context Configured to Process this Request". It does this until you request http://hostname:8080/ or http://hostname:8080/index.html at which point http://hostname:8080 resolves to http://hostname:8080/index.html. I subsequently tried the same from a colleagues Linux Mandrake machine on the same LAN via the IP (the server hostname does not resolve on his machine, even for ping) in this instance http://hostname:8080 resolved directly to http://hostname:8080/index.html. I have not tried this before getting MSIE6 to resolve the address and so its unclear as to whether this is a MS problem or a problem with the server. In all cases the machines had been freshly booted and were communicating for the first time. It seems though that Tomcat can't figure out some URI aliases until after the first sucessful request to an alias that includes the full or partial path. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
