EiffelStudio 14.05 comes with EWF version 0.4: there is nothing to do in this case.
-If you are using an older version of EiffelStudio, we recommand to download the latest EWF version (0.4 as of this writing) instead of using the one that comes with EiffelStudio.
+Latest EiffelStudio release comes with latest EWF version: there is nothing to do in this case.
+If you are using an older version of EiffelStudio, we recommand to download the latest EWF version ({{ site.version }} as of this writing) instead of using the one that comes with EiffelStudio.
Follow these steps to download and install EWF on your computer:
Framework to build web applications in Eiffel
diff --git a/workbook/basics/basics.md b/workbook/basics/basics.md index 6c7ea7e5..ad19ff47 100644 --- a/workbook/basics/basics.md +++ b/workbook/basics/basics.md @@ -97,11 +97,11 @@ The **WSF_RESPONSE** provides features to define the response with information s **APPLICATION** is the root class of our example, it launches the application, using the corresponding connector, Which connector? this depends how you want to run it cgi, fcgi,nino or standalone. For development is recommended to use a standalone web server written in Eiffel, and run the execution within the EiffelStudio debugger. For production fcgi (or cgi) using Apache or another popular web server. - + **WS_LAUNCHABLE_SERVICE** inherit from **WS_SERVICE** class, which is a marker interface in EWF. And also provides a way to launch our application using different kind of connectors. The class **WSF_DEFAULT_SERVICE_I**, inherit from **WS_LAUNCHABLE_SERVICE** and has a formal generic that should conform to **WSF_SERVICE_LAUNCHER [WSF_EXECUTION]**. Below a [BON diagram](http://www.bon-method.com/index_normal.htm) showing one of the possible options. - + Other connectors: **WSF_STANDALONE_SERVICE_LAUNCHER** @@ -115,7 +115,7 @@ The **APPLICATION_EXECUTION** class inherits from **WSF_EXECUTION** interface, In the **APPLICATION_EXECUTION** class class you will need to implement implement the **execute** feature, get data from the request *req* and write the response in *res*. - + The WSF_EXECUTION instance, in this case ```APPLICATION_EXECUTION``` is created per request, with two main attributes request: ```WSF_REQUEST``` and response: ```WSF_RESPONSE```. diff --git a/workbook/deployment/readme.md b/workbook/deployment/readme.md index 21020166..12958fd5 100644 --- a/workbook/deployment/readme.md +++ b/workbook/deployment/readme.md @@ -133,10 +133,13 @@ Copy the app.exe and the folder "www" into a folder served by apache2, for exam >NOTE: By default Apache does not come with fcgid module, so you will need to download it, and put the module under Apache2/modules -#.htaccess FCGI ->http://perishablepress.com/stupid-htaccess-tricks/ +# .htaccess FCGI -####.htaccess +``` +http://perishablepress.com/stupid-htaccess-tricks/ +``` + +#### .htaccess Options +ExecCGI +Includes +FollowSymLinks -Indexes diff --git a/workbook/handling_request/headers.md b/workbook/handling_request/headers.md index 9c5740b1..6ed242a7 100644 --- a/workbook/handling_request/headers.md +++ b/workbook/handling_request/headers.md @@ -452,7 +452,7 @@ As an exercise, try to write a similar service to retrieve the OS family using t * [SERVER_SOFTWARE](https://tools.ietf.org/html/rfc3875#section-4.1.16) **Example** -An [EWF service](../cgi_variables/application.e) that shows the CGI variables, creates a table showing the values of all the CGI variables. +An [EWF service](../headers/cgi_variables/application.e) that shows the CGI variables, creates a table showing the values of all the CGI variables. Nav: [Workbook](../../workbook) :: [Handling Requests: Form/Query parameters](../form) :: [Generating Responses](../../generating_response/generating_response)