Diferencia entre revisiones de «Apache»

De MoodleDocs
Sin resumen de edición
(Updated as per 3.5 page)
 
(No se muestran 12 ediciones intermedias de 3 usuarios)
Línea 1: Línea 1:
Cuando la mayoría de la gente se refiere a "Apache", están hablando acerca del Servidor de HTTP de Apache. Aunque en efecto, hablar de Apache es referirnos realmente a la Fundación de Software Apache, la cual aloja una gran cantidad de proyectos, de los cuales el Servidor HTTP es solo uno, posiblemente el más conocido.
{{Pendiente de traducir}}
{{Instalación de Moodle}}
'''Este artículo se refiere al 'Servidor Apache HTTP''''


El Servidor HTTP de Apache permite que las páginas Web sean publicadas en la Internet (o en una intranet o incluso en una máquina de pruebas). El lenguaje de programación PHP, bajo el cual Moodle esta desarrollado, está íntimamente integrado con el servidor HTTP. Un servidor Web es un componente requerido en la instalación de Moodle. Hay dos versiones del Servidor HTTP de Apache, la versión 1 y la versión 2. Aunque la Versión 2 debería haber remplazado a la versión 1, las arquitecturas son tan diferentes que ambas continúan siendo soportadas. Incluso tienen soporte completo para PHP y Moodle.
The Apache HTTP server is the software that (along with the PHP scripting language) 'runs' Moodle. Note that there are alternatives (e.g. IIS on Windows) but the Apache HTTP Server is very popular on all platforms.  


El proyecto del Servidor HTTP de Apache se describe asimismo de la siguiente manera:
== Instalación de Apache ==
Installers are available for most platforms from http://httpd.apache.org/download.cgi. The official installation instructions are here: http://httpd.apache.org/docs/2.0/install.html. If you are running Linux then you are recommended to use the packaged version if you can. For example in Debian/Ubuntu it is simply:
<pre>
sudo apt-get install apache2
</pre>


"El proyecto del Servidor HTTP de Apache es un esfuerzo para desarrollar y mantener un software de servidor HTTP de código abierto para sistemas operativos modernos, incluyendo UNIX y Windows NT. La meta de este proyecto es proveer un servidor de servicios HTTP seguros, eficientes y extensibles en sincronía con los actuales estándares de HTTP.
See the documentation for your particular platform for the instructions. Apache is straightforward to build from source if you have to and the PHP documentation contains an article on building both Apache and PHP together - although you should rarely need to do that.


Apache ha sido el software de servidor Web para Internet más popular, desde abril de 1996. En noviembre del 2005, la encuesta de servidores Web de Netcraft encontró que más del 70% de los sitios Web sobre Internet estaban usando Apache, haciendo esto de manera más completa que todos los otros servidores Web combinados.
==Desempeño==


Vea [[Recomendaciones sobre desempeño]]


== Instalando Apache ==
==Slasharguments==


Actualmente Apache puede ser instalado de manera conjunta con PHP y MySQL, que en combinación son conocidos como la tecnología AMP.
The function ''slash arguments'' is required for various features in Moodle to work correctly, as described in [[Usando slash arguments]].
Vea [[Instalación AMP]] para detalles.


To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory:


== Vea también ==
AcceptPathInfo On
 
Note: When using ".htaccess" in your local Moodle install folder, you should include/enable "AllowOverride Directive" in "httpd.conf", first.
Also! please note that using .htaccess file will cause performance hit on your server!
 
If you are using 1and1 as a hosting company the above does not work.  The solution is to create a php.ini file in the moodle directory with this content:
 
cgi.fix_pathinfo = 0
 
It was a know bug when using PHP as CGI.
 
==SSL==
 
Moodle has an option to enable HTTPS for the whole site or for just the login pages; either option requires that your web server is configured for SSL.
 
* Whole site HTTPS is enabled by including the https:// schema in your config.php 'wwwroot' parameter.
* Login only HTTPS is enabled by setting the 'loginhttps' parameter, where the wwwroot schema should remain as http://
 
NOTE: Login only https was deprecated and removed from Moodle 3.4: https://tracker.moodle.org/browse/MDL-42834
 
Login only https is available in Moodle 3.3 and earlier in the admin interface via Administration>Security>HTTP Security and checking the button. (Note the warning and see ssl section below)
 
Prior to Moodle 2.3 It was not advised to run the whole site over HTTPS due to legacy restrictions with client-side caching. This is no longer the case assuming client browsers support the 'Cache-Control: public' method, which all supported browsers for this version of Moodle do.
 
To use HTTPS you will need to obtain an SSL certificate, you have two options:
 
* Generate a self-signed certificate. This is fine on (say) an Intranet but unsuitable for the public internet, but users will we warned the certificated is untrusted when used publicly.
* Purchase a certificate from a vendor. There is a surprising range of prices and value-added services available. Some hosting companies even provide free certificates.
 
Debian provides instructions for installing a self-signed certificate [https://wiki.debian.org/Self-Signed_Certificate on their wiki] and includes general information on configuring Apache for SSL.
If you purchase a vendor certificate you will normally receive instructions for installing it.
 
A basic Apache SSL configuration can be summarised as:
 
Listen 443
NameVirtualHost *:443
<VirtualHost *:443>
    SSLEngine On
    SSLCertificateFile /path/to/your/certificate.crt
    SSLCertificateKeyFile /path/to/your/certificate.key
    ...
</VirtualHost>
 
== See also ==


* [http://httpd.apache.org/ The Apache HTTP Server Project homepage]
* [http://httpd.apache.org/ The Apache HTTP Server Project homepage]
* [http://en.wikipedia.org/wiki/Apache_HTTP_Server Wikipedia article on the Apache HTTP Server]
* [http://en.wikipedia.org/wiki/Apache_HTTP_Server Wikipedia article on the Apache HTTP Server]
* [http://httpd.apache.org/docs/2.0/misc/perf-tuning.html Apache Performance Tuning article at the official homepage]
* [https://els.earlham.edu/cayaraa/weblog/1468.html Making Moodle work with SSL]
* [http://www.krufix.de/ Using the same Moodle twice in local network and Internet via SSL-Proxy] (in German)


[[Category:Administrador]]
[[ja:Apache]]
[[Category:Desarrollador]]
[[de:Apache]]
[[en:Apache]]
[[en:Apache]]

Revisión actual - 16:37 14 ago 2018

Nota: Pendiente de Traducir. ¡Anímese a traducir esta página!.     ( y otras páginas pendientes)

Este artículo se refiere al 'Servidor Apache HTTP'

The Apache HTTP server is the software that (along with the PHP scripting language) 'runs' Moodle. Note that there are alternatives (e.g. IIS on Windows) but the Apache HTTP Server is very popular on all platforms.

Instalación de Apache

Installers are available for most platforms from http://httpd.apache.org/download.cgi. The official installation instructions are here: http://httpd.apache.org/docs/2.0/install.html. If you are running Linux then you are recommended to use the packaged version if you can. For example in Debian/Ubuntu it is simply:

sudo apt-get install apache2

See the documentation for your particular platform for the instructions. Apache is straightforward to build from source if you have to and the PHP documentation contains an article on building both Apache and PHP together - although you should rarely need to do that.

Desempeño

Vea Recomendaciones sobre desempeño

Slasharguments

The function slash arguments is required for various features in Moodle to work correctly, as described in Usando slash arguments.

To turn it on, add this line to your httpd.conf, or to a .htaccess file in your local directory:

AcceptPathInfo On

Note: When using ".htaccess" in your local Moodle install folder, you should include/enable "AllowOverride Directive" in "httpd.conf", first. Also! please note that using .htaccess file will cause performance hit on your server!

If you are using 1and1 as a hosting company the above does not work. The solution is to create a php.ini file in the moodle directory with this content:

cgi.fix_pathinfo = 0

It was a know bug when using PHP as CGI.

SSL

Moodle has an option to enable HTTPS for the whole site or for just the login pages; either option requires that your web server is configured for SSL.

  • Whole site HTTPS is enabled by including the https:// schema in your config.php 'wwwroot' parameter.
  • Login only HTTPS is enabled by setting the 'loginhttps' parameter, where the wwwroot schema should remain as http://

NOTE: Login only https was deprecated and removed from Moodle 3.4: https://tracker.moodle.org/browse/MDL-42834

Login only https is available in Moodle 3.3 and earlier in the admin interface via Administration>Security>HTTP Security and checking the button. (Note the warning and see ssl section below)

Prior to Moodle 2.3 It was not advised to run the whole site over HTTPS due to legacy restrictions with client-side caching. This is no longer the case assuming client browsers support the 'Cache-Control: public' method, which all supported browsers for this version of Moodle do.

To use HTTPS you will need to obtain an SSL certificate, you have two options:

  • Generate a self-signed certificate. This is fine on (say) an Intranet but unsuitable for the public internet, but users will we warned the certificated is untrusted when used publicly.
  • Purchase a certificate from a vendor. There is a surprising range of prices and value-added services available. Some hosting companies even provide free certificates.

Debian provides instructions for installing a self-signed certificate on their wiki and includes general information on configuring Apache for SSL. If you purchase a vendor certificate you will normally receive instructions for installing it.

A basic Apache SSL configuration can be summarised as:

Listen 443
NameVirtualHost *:443
<VirtualHost *:443>
    SSLEngine On
    SSLCertificateFile /path/to/your/certificate.crt
    SSLCertificateKeyFile /path/to/your/certificate.key
    ...
</VirtualHost>

See also