http://www.prolix.ro/dokuwiki/ Fri, 30 Oct 2009 05:13:18 -0700 FeedCreator 1.7.2-ppt DokuWiki http://www.prolix.ro/dokuwiki/lib/images/favicon.ico http://www.prolix.ro/dokuwiki/ http://www.prolix.ro/dokuwiki/documentation:goahead:64bit?rev=1110713275&do=diff The following files need to be changed for 64 bit compatibility: asp.c * Line 100 - ejSetUserHandle(ejid, (int) wp); + ejSetUserHandle(ejid, wp); * Line 183 - rc = scriptEval(engine, nextp, &result, ejid); + rc = scriptEval(engine, nextp, &result, (void*) ejid); documentation:goahead Sun, 13 Mar 2005 03:27:55 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:comparison?rev=1142497356&do=diff A feature comparison between various embedded and non-embedded web servers. Please append your experiences if you have worked with any of the webservers listed. One way to class the web servers is by the request processing method, we have 2 categories: documentation:goahead Thu, 16 Mar 2006 00:22:36 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:cookies?rev=1110100735&do=diff Example from jklee, 2001/8/31 Using in process CGI: /* in-process CGI append this code to main.c */ static void sampleCookieFor(webs_t wp, char_t* path, char_t* query) { websWrite(wp, T("HTTP/1.0 200 OK\n")); websWrite(wp, T("Server: GoAhead-Webs\r\n")); websWrite(wp, T("Pragma: no-cache\n")); websWrite(wp, T("Cache-control: no-cache\n")); websWrite(wp, T("Content-Type: text/html\n")); websWrite(wp, T("Set-Cookie: name=jklee; path=/; expires=Wednesday, 29-Nov-02 2… documentation:goahead Sun, 06 Mar 2005 01:18:55 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:cookies_asp?rev=1111082516&do=diff by Peter Foti, 2002/02/04 We explain here how to manipulate cookies with: * server side functions for getting the cookie. * client side javascript code for setting, getting and deleting the cookies. Some of this code is almost a duplication of the websGetRequestDir function. documentation:goahead Thu, 17 Mar 2005 10:01:56 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:design?rev=1132492541&do=diff This topic is really complex. Will try to cover in this section the most common technologies suitable for web interface design using the GoAhead webserver focusing on websites that need dynamic update at regular intervals. Before choosing an implementation method make sure you understand the following limitations: documentation:goahead Sun, 20 Nov 2005 05:15:41 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:ecos?rev=1127401347&do=diff Source: news.goahead.com, Information collected from various developers posted on the newsgroup. If someone knows more about this please post here. David Tiktin, 2004/11/24 First make sure that you read all the information needed for the development process under eCos. documentation:goahead Thu, 22 Sep 2005 08:02:27 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:faq?rev=1171414336&do=diff Sessions No the webserver does not have support for this feature. The developer will have to implement it's own client tracking method. There are two methods to solve this: * Store the session data on the server * Store the session data on the client (cookies) documentation:goahead Tue, 13 Feb 2007 16:52:16 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:feedback?rev=1132325318&do=diff I would like to know more about: * Security Scan results of GoAhead by programs like Nessus and associations of tests and patches. 2005/09/28 admin: I'm not sure I understand this one, you want results of scans using these type of tools? In the newsgroup there is a reference about scans run with the ISS tool, there is a thread started on Jan 30 2004 with the subject ISS vulnerabilities of High and Medium severity is this what you are looking for? documentation:goahead Fri, 18 Nov 2005 06:48:38 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:general?rev=1256067546&do=diff This section covers the history of GoAhead Webserver and information about previous releases. Currently the GoAhead web server is in bugfix mode no new features are planned. Comparison - see this page for a quick assessment of capabilities compared to other embedded and non-embedded web servers. documentation:goahead Tue, 20 Oct 2009 12:39:06 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:howto?rev=1175286338&do=diff This wikipage is dedicated to GoAhead Open Source Embedded Webserver. For more information visit the main page. On Unix systems (like Linux) if the webserver is started from the command line it will stop working after closing the terminal. There are 2 methods to avoid this to happen: documentation:goahead Fri, 30 Mar 2007 13:25:38 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:postbug?rev=1149842283&do=diff We collect here information about the POST CGI bug in GoAhead webserver 2.1.8. A copy of relevant posts on news.goahead.com together with Subject, Author and Date is available for reference. Please append your feedback at the end of the file. When the server receives a POST which contains more then 2400 bytes in the “content”, the file for the “cgi” (wp->cgiStdin) is not properly written. (It does not happen all the time...) documentation:goahead Fri, 09 Jun 2006 01:38:03 -0700 http://www.prolix.ro/dokuwiki/documentation:goahead:sessionscsyap?rev=1114183279&do=diff Source: [Yap/csyap], 2000/1/20 Browsing session (or user “state”) plays a essential role in Web application development, a browsing session is started by assigning a unique session id to each incoming user, this session id must be send to webserver during the whole browsing session, normally session id is stored in cookie or embedded in the URL, i found both have drawbacks, cookie could be refused by browser, and travel the session id in URL makes the URL messy and worse, all the links in your … documentation:goahead Fri, 22 Apr 2005 08:21:19 -0700