[lighttpd] Web server (to replace Mongoose)

kevindickinson

kevindickinson

Active Member
af123 said:
When you select the 'mobile version' link on the main page, that takes you to http://humax/m/. mongoose looks in the directory first for a file called index.shtml which contains a redirect to /m/index.jim. That means the first time you see the mobile menu your browser is pointing at /m/index.jim. Lighttpd looks for index.jim first so the browser stays at /m/. When you click on the home icon, then you're on /m/index.jim.

It's just a configuration difference between the two but that's why you're seeing slightly different behaviour. You're right in that the underlying problem is a coding error. I'm upgrading to the latest version of jquery mobile and will rejig the code around to fix things before the next release.
Click to expand...

Thanks for the explanation - nice to understand a bit of what is going on
 
kevindickinson

kevindickinson

Active Member
Also thanks for adding the server (lighttpd or mongoose) after the version number on webif page makes it much easier to work out which version I've got live when testing
 
W

wubweku

New Member
Been a while since I was here - I noticed that I was way out of date on the custom firmware so upgraded to the latest version for 1.02.20, then did the load of the latest web-if etc. Lots of packages downloaded and upgraded. Rebooted the hummy then only got a directory listing for mongoose when I connected the browser. Didn't know it was mongoose initially, but after a telnet and find, I worked it out. No index page existed or anything. Anyway, found this thread and figured I have nothing to lose by installed lighttpd, now everything is back up and running. Yay. Thanks for all the hard work guys. :D
 
martxw

martxw

Active Member
Just got around to reconfiguring the SSL on my machine.
Edited /mod/etc/lighttpd/extra.conf for an extra SSL port, and replaced /mod/etc/webif.pem with the certificate file containing my certificate details.
The certificate file is exactly the one I previously had with Mongoose.
Before, browsers always reported the certificate as having an untrusted chain. Now they're reporting that it's OK. So good progress there. Cheers!
 
OP
af123

af123

Administrator
Staff member
martxw said:
Before, browsers always reported the certificate as having an untrusted chain. Now they're reporting that it's OK. So good progress there. Cheers!
Click to expand...
Perhaps the pem file you're using contains an intermediary certificate alongside your server certificate to complete the trust chain and Mongoose wasn't serving that. It's an unexpected bonus anyway! : )
 
OP
af123

af123

Administrator
Staff member
lighttpd seems to be working well for everyone and we've ironed out a couple of minor issues. I'll release webif 1.0.13 later on today and that will automatically upgrade everyone to lighttpd. I just need to test that automatic upgrade process and the initial bootstrap first.

Thanks everyone who took the time to give it a try.
 
D

damianiw

Member
Hi

I'm currently running :

Web interface version: 1.2.5-13
Custom firmware version: 3.03 (build 2368)
Humax Version: 1.03.12 (kernel HDR_CFW_3.03)

Both lighttpd and mongoose are showing in my installed packages, is this correct or should I remove mongoose ? I do have the mobile package installed so maybe that's why ?
 
OP
af123

af123

Administrator
Staff member
It's now safe to remove mongoose although you may find that some packages depend on it and will prevent removal. The mobile package is deprecated and, as far as I know, no longer works properly. There is a mobile version built into the main webif package.
 
You must log in or register to reply here.
Top