EmbedThis GoAhead^™ FAQ

The GoAhead WebServer was originally written by Michael O’Brien, CEO of Embedthis and it remains a very popular to this day. With the acquisition of GoAhead by Oracle, Oracle asked Embedthis to support existing GoAhead WebServer customers and to offer commercial licenses for the GoAhead WebServer.

The GoAhead WebServer is a simple, compact web server that has been widely ported to many embedded operating systems. Ioto is faster, smaller and more modern. We recommend all new projects use Ioto as their device agent.

Yes. GoAhead has build-time configuration settings to select required features and minimize memory footprint. See Building from Source for details of the configuration options.

You need to increase the LimitRequestBody limit in the goahead.conf file. This imposes a maximum upload file size. Some samples have a MAX_FILE_SIZE input field in the HTML form. This however, is just a hint to the browser, and is only processed by some browsers.

Yes. When GoAhead is built from source, a single bld.h header controls exactly what features and modules are built into the server. For example, if you don’t require SSL support, and you wish to minimize memory footprint, you can run:

./configure –without ssl

Run goahead or winGoAhead with the logging switch “-l”. The logging switch takes the following parameters:

goahead -l logName[:logLevel]

Where logLevel is a number between 0 and 9. Zero is the least verbose. To debug HTTP requests, a level of 6 provides the detail of all the request / response exchanges.