Is an Open Source dual license mode Embedded Web server.
Here you will find various information collected from GoAhead, response to your FAQ, HOWTO's and other useful information. In many cases information about the author and date when the information was posted to the newsgroup is available for reference.

Remember:

• The intent of this wiki is to collect and host information not covered by the documentation.
• Since this is a wiki you too can add or modify existing content directly with EDIT, update sections with new information or make corrections.
• Comments, questions, suggestions for improvement should be sent to the site admin.

If you are looking for consulting services related to GoAhead WebServer you can go to this page.

Update 2007/12/08 : The GoAhead NewsGroup is no longer available. that's a real bummer.

Before you start browsing make sure you understand the following:

1. This site is in no way connected to GoAhead.
2. I can not guarantee, in any way, the validity of the information published.
3. None of the authors can be held responsible for any information published, linked on this site or for the use of this information.
   Please do not publish on this site information that violates the license and/or copyright of GoAhead Software. Such information will be deleted and your IP address ban-ed.
4. For official information and technical support about the product visit: GoAhead Webserver home page

Browse the following sections to find answers to your questions:

• GENERAL
• FAQ
• HOWTO

A feature comparison against other embedded and non-embedded web servers:

• COMPARISON

Best methods for dynamic website design using the GoAhead web server for serving data:

• DESIGN

Tune into latest changes with the RSS XML feed:

• RSS FEED

If you want to see also other information on this site either add it or request it here:

• FEEDBACK

This section includes tutorials and howto's that are platform specific.

This is a supported platform, make files shipped with the release package.

The default environment does not offer adequate support for running the web server.
See this document VxWorks system configuration for more information.

There are reports of “flaky” behaviour under this platform like:

1. web server stop responding for a period of time (probably caused by insufficient memory available).
2. problems with WEBS_KEEP_ALIVE compile flag enabled.

This is a supported platform, make files shipped with the release package.

Release 2.1.8 has a bug in the socket handling routines so it will not work as expected (although it compiles without problems).
This link explains the problem and how to fix the fd_mask size problem.

Information on how to build the GoAhead web server on this platform:

1. Dr. Dobbs Journal has an article by Anthony J. Massa on Integrating GoAhead WebServer & eCos.
   Subscription required to access the article.
2. other information collected from the newsgroup can be found here.

For people new to this platform there is:

• Embedded software development with eCos a reference manual by Anthony J. Massa. Here is another link to the Phptr page that has also source code and figures.
• Another article by Anthony J. Massa

Mailing list:

• Ecos discuss mailing list at RedHat or Sourceware.

sandeep, 2002/10/22

I didn't find support for ECOS ROMFS in GoAhead for storing static web pages (I looked at both 2.1.4 and 2.1.1).
I have added and modified some files: source code package.

At compile time you can choose between WebROM or ECOS ROMFS.

This is a supported platform, make files shipped with the release package.

Author: K.F.Lin

Besides the default build that comes with the web server there is http://www.geocities.com/dennykf/prog/webs/index.html
You can find there the necessary files to compile WinCE ver. 2, 3 for the MIPS, SH3 and StrongARM architectures and there are also precompiled binaries for all these platforms.

This is a supported platform, make files shipped with the release package.

The Makefile shipped in the latest version (2.1.8) does not specify correctly the compiler name. This is a problem with uClinux builds, when doing cross-compilation because the wrong compiler will be used.

The following change to LINUX/Makefile will fix this issue:

--- ../../../goahead.2.1.8/LINUX/Makefile       2003-12-02 22:13:57.000000000 +0200
+++ ./Makefile  2005-10-28 23:58:42.120636231 +0300
@@ -152,4 +152,4 @@
 #      Transition rules (add -o to put object in right directory)
 #
 .c.o:
-       cc -c -o $@ $(DEBUG) $(CFLAGS) $(IFLAGS) $<
+       $(CC) -c -o $@ $(DEBUG) $(CFLAGS) $(IFLAGS) $<

If you run/test the web server code on the x86 architecture you can use Valgrind to debug memory problems like buffer overruns, leaks and other problems.

Platform not officially supported in the latest release 2.1.8 of the GoAhead WebServer.

Author: Gisle Vanem

Build using djgpp compiler and Watt-32 TCP/IP stack.
Apply first this 2.1.8 patch to the original sources. Builds with OpenSSL too.

Platform not officially supported in the latest release 2.1.8 of the GoAhead WebServer.

Author: Simon Byholm

See this link for information on how to port the GoAhead WebServer for this platform.