Late post: Email to sourceforge.net has been delayed by SF/RR policy issues. Reply already sent to Charles. See below for final post in this thread.
On Sat, 2004-10-02 at 16:28, Charles Steinkuehler wrote: > Calvin D. Webster wrote: > > > Charles Steinkuehler wrote: > > > >> Forgot to cc: list... > >> > >> Calvin Webster wrote: > >> > >>> On Fri, 2004-10-01 at 15:02, Martin Hejl wrote: > >>> > >>>> Calvin Webster wrote: > >>>> > Has anyone had problems rendering the LEAF status pages in > >>>> Mozilla? > All I get in the Mozilla 1.4.2 browser window is the > >>>> plain-text source > >>>> > of the main page. However, if I bring it up in MSIE it works fine. > >>>> That's a known issue - please replace the sh-httpd lrp on the floppy > >>>> with the version from the packages page at: > >>>> http://leaf.sourceforge.net/mod.php?mod=userpage&menu=91017&page_id=51 > >>> > >>> > >>> I downloaded and replaced ssh-httpd.lrp before realizing it was the same > >>> version as in the distibution. It still doesn't work in my Mozilla 1.4.2 > >>> browser. > >>> > >>> Maybe, as Erich implied, the issue is resolved for Mozilla 1.6b and > >>> above. > >>> > >>> I'll try updating my browser. > >>> > >>> Thanks for the feedback. > >> > >> > >> It could be a problem with sh-httpd returning an incorrect mime-type, > >> which > >> Mozilla will honor, but IE will typically ignore (in favor of > >> auto-detecting > >> the file type). > >> > >> If possible, can you provide the output provided by connecting > >> directly to > >> sh-httpd with the netcat (nc) command? > >> > >> echo -e "GET / HTTP/1.0\r\n\r\n" | nc <weblet-IP> 80 > >> > >> You should get the html source of the weblet index page, complete with > >> the > >> headers (which includes the Content-Type header). Use > >> <shift><page-up> to > >> scroll back to the headers, or pipe the output to a file, ie: > >> > >> echo -e "GET / HTTP/1.0\r\n\r\n" | nc <weblet-IP> 80 >debug.txt > >> > >> ...and look at the results with an editor. If the Content-Type header > >> doesn't indicate html, your problem is with sh-httpd, not Mozilla. > >> > > Actually, that's all I get is the html source in the Mozilla browser. > > There is no "Content-Type" header element contained in the weblet page. > > There are, however, a "<!DOCTYPE" header line and opening and closing > > <html> tags. The "nc" output indicates, however, that the "Content-type" > > is being interpreted as "text/plain". Below I've inserted the header > > portion of the output from the command suggested above. > > > > ####################### > > ## Begin "nc" Output ## > > ####################### > > > > HTTP/1.0 200 OK > > Server: ShellHTTPD/0.4.1 > > Date: Sat, 02 Oct 2004 15:22:01 GMT > > Connection: close > > Content-type: text/plain > > Content-length: 13143 > > Last-modified: Fri Aug 13 05:58:43 2004 > > > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > > <html><head><title>Bering-uClibc LEAF Firewall</title> > > <link rel="stylesheet" type="text/css" href="weblet.css"> > > </head> > > > > > > ##################### > > ## End "nc" Output ## > > ##################### > > The "Content-type: text/plain" header is what's tripping up Mozilla, which > (correctly) displays the HTML source as plain text (since that's what the > web-server told it to do). This means your problem is with the > configuration of sh-httpd on your LEAF box. Make sure you're using the > latest version (IIRC, some changes have been made recently to the packaging > of weblet/sh-httpd). You can also check the mime-types file for sh-httpd, > possibly fixing the problem yourself (I had setup sh-httpd to default to > text/plain for unknown mime types, but Bering could be doing things > differently). See my web-page on sh-httpd (as well as any Bering specific > documentation...the Bering manuals are quite extensive, and very well written): > http://lrp.steinkuehler.net/Packages/weblet.htm > http://lrp.steinkuehler.net/Packages/man/sh-httpd.readme > > See the readme file, above, for details about the DEFCONTENT and MIME_TYPES > settings in the sh-httpd.conf file. I suspect one of these settings (or one > of the mime-type files referenced by MIME_TYPES) is causing your problem. That led me to find the problem. Apparently, the "sh-httpd.mime" file is missing from the sh-httpd.lrp package in the "Bering-uClibc_2.2_img_bering-uclibc-1680.bin" image I downloaded last week. The package "ssh-httpd.lrp" version 1.2.5 Rev 3 on the "Bering-uClibc Packages" download page does now contain this file in "etc/". Also, the latests release of Bering-uClibc 2.2.1 does contain the file. Thank you Charles. --Cal Webster ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
