in the appWeb.conf and this page is shown if no page is found (and when someone does not
add a page in the url.

to:

A workaround is to set the 404 to the default (index) page ! Put the line
ErrorDocument 404 /default.html in the appWeb.conf and this page is shown if no page is found (and when someone does not add a page in the url.

October 07, 2008, at 05:39 PM
by mafo -- workaround 2.1.0.1 not found bug

Changed lines 20-25 from:

to:

A workaround is to set the 404 to the default (index) page ! Put the line:
ErrorDocument 404 /default.html
in the appWeb.conf and this page is shown if no page is found (and when someone does not
add a page in the url.

Bug in 2.1.0-1

I installed this in march so for people who just started the ipkg install, this bug will cause indexes not to work. For example instead of seeing index.html after starting you will get a 404 error. This error is found in this link http://www.appwebserver.org/forum/viewtopic.php?t=597&highlight=index
If you want appweb you need to install the previous version.

This is because before the binary version of bldout is created a symlink is created to the busybox 'cat'. But, in doing so, busybox can't tell what binary is being called and complains. Ignore the messages and let it continue, they will clear up eventually when the binary version of bldout has completed.

I have managed to build appWeb natively and also built it with PHP and run some scripts with a bit of hacking around, although the php libs are not properly located and more complicated scripts fail.

I have not managed to get appweb 2.0.x building and running properly yet.

For more information look at the mailing list archives where I documented the progress in some detail.

April 16, 2005, at 07:57 PM
by MattMcNeill -- Experience of trying to natively compile appWeb

Changed lines 122-125 from:

I found that the httpPassword utility doesn't work because some libraries have been missed from the ipkg (namely libmpr.so). I have only got a native build environment working, and appWeb will only build on i386 due to the fact that its build scripts use two binaries (bldout and genDepends - from FSF, stallman) and the sources are not provided (neither could I find them on google) so I hit a dead end there.

I'm now looking at thttpd.

to:

I found that the httpPassword utility doesn't work because some libraries have been missed from the ipkg (namely libmpr.so). I have only got a native build environment working, and I've hit a dead end. I got as far as:

followed setting up the native compilation environment for unslung packages

did make appweb

build failed since downloaded source contains two binary files (bldout and genDepend) which need to be deleted so that the bootstrap configure builds them natively.

did make appweb

build failed since /dev/null was read only on unslung 3.17. Made it a+rw.

did make appweb

got a lot further then hit a funny problem with busybox in some make files. I isolated it within an example makefile rules.mk which has a line:

I found that the httpPassword utility doesn't work because some libraries have been missed from the ipkg (namely libmpr.so). I have only got a native build environment working, and appWeb will only build on i386 due to the fact that its build scripts use two binaries (bldout and genDepends - from FSF, stallman) and the sources are not provided (neither could I find them on google) so I hit a dead end there.

First you have to change the port of the current web server that does the NSLU2 management pages.

Bring up in a browser the NSLU2 management pages. By default it is 192.168.1.77.

Click on Administration (it may ask you for the username and password)

On the submenu under Administration click on System

Scroll all the way down to the bottom of the page to the Location section.

Under the second check box (Enable UPnP? Support) there is a box with the number 80 in it. Change that number to something like 8080 so the management pages will be on port 8080. So now when you need to pull up the management pages you need to type in something like this: 192.168.1.77:8080

Click on the Save button at the bottom of the page. It will make the change immediately so if you try to click on anything else you will get an error from the browser. Just go to the url that you typed in to get to these pages and put :8080 after the ip address and you should be working again.

One thing that will stop it from running is not having the Openssl and Openssh packages installed.
If you don't want to use these packages you will need to edit the appWeb.conf file and comment out the entries for Openssl and Openssh.

AppWeb is a very fast, small-footprint, standards-based, portable server, specifically developed for use by embedded devices and applications.

to:

AppWeb is a very fast, small-footprint, standards-based, portable server, specifically developed for use by embedded devices and applications. More information can be had on http://www.appwebserver.org/