EmbedThis GoAhead™ FAQ
This is a selection of some of the more frequently asked questions about EmbedThis GoAhead.
If you don’t find the answers you need here, please consult the product documentation or contact us on Chat at the bottom right of this page.
Why is Embedthis Software supporting and distributing the GoAhead WebServer
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.
How does the GoAhead WebServer compare with Ioto
Can I disable features to minimize memory footprint at run-time
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.
How can I upload large files
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.
When I build the source, can I disable features at compile time
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
How can I trouble-shoot with trace
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.
Comments