#apache module

How to install Apache module mod_limitipconn.c on linux server ?

  Apache module mod_limitipconn.c is a module which allows web server administrators to limit the number of simultaneous downloads permitted from a single IP address.

    To set the IP limit on the server using mod_security.

Check apache version first on server.

httpd -v

Go to the below path

cd /usr/local/src/

Download the mod_limitpconn using the below link. I am having apache version 2.2.22.…

How to Install mod_pagespeed in cpanel

        Login to the server via SSH

Go to below folder

cd /usr/local/src

create directory

mkdir mod_pagespeed

Download pagespeed rpm

wget https://dl-ssl.google.com/dl/linux/direct/mod-pagespeed-beta_current_i386.rpm

Extract the rpm

rpm2cpio mod-pagespeed-beta_current_i386.rpm | cpio -idmv

Copy the modules to apache modules folder

cp…

mod_rewrite on URLs with question marks

forward:

https://domain.com/acquisitions/viewLead.gsp?employerId=201

to

https://domain.com/acquisitions/viewLead/viewLead/201

Because of the question mark Query String should be used.

RewriteEngine On RewriteCond %{QUERY_STRING} ^employerId\=([0-9]+) RewriteRule acquisitions/viewLead.gsp$ /acquisitions/viewLead/viewLead/%1? [R=301]

SEO rood domain redirect to www

To redirect to an internal address, one can preserve the URL with a regular mod rewrite P-Flag. But to redirect to an outside address you will get a 403 forbidden if you do it with the P-Flag. In that case, you have use mod_proxy as follows:

To redirect www.domain.com/search to http://domain.everyzing.com/ and mask the url (have apache act as a gateway)

ProxyRequests Off ProxyPreserveHost Off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass /search http://domain.everyzing.com/ ProxyPassReverse /search http://domain.everyzing.com/

Note that we need to run the following first

New Post has been published on http://mocco.sk/using-mod_spdy-with-apache2-on-centos-6-4/

Using mod_spdy With Apache2 On CentOS 6.4

Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Follow me on Twitter Last edited 03/20/2013

SPDY (pronounced “SPeeDY”) is a new networking protocol whose goal is to speed up the web. It is Google’s alternative to the HTTP protocol and a candidate for HTTP/2.0. SPDY augments HTTP with several speed-related features such as

stream multiplexing and header compression. To use SPDY, you need a web server and a browser (like Google Chrome and upcoming versions of Firefox) that both support SPDY. mod_spdy is an open-source Apache module that adds support for the SPDY protocol to the Apache HTTPD server. This tutorial explains how to use mod_spdy with Apache2 on CentOS 6.4.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

SPDY runs over HTTPS, so we need an HTTPS-enabled web site to test SPDY. Please note that SPDY will fall back to HTTPS if the user’s browser does not support SPDY or if things go wrong, so installing mod_spdy doesn’t hurt your existing setup.

I’m assuming that you have a working LAMP setup, as described on Installing Apache2 With PHP5 And MySQL Support On CentOS 6.4 (LAMP).

For testing purposes I will simply use the default SSL web site that comes with the Apache package on CentOS (you don’t need to do this if you already have an SSL web site on your server). If you have no SSL web site, you can enable the default SSL web site as follows:

yum install mod_ssl openssl

openssl genrsa -out ca.key 4096

openssl req -new -key ca.key -out ca.csr

openssl x509 -req -days 365 -in ca.csr -signkey ca.key -out ca.crt

cp ca.crt /etc/pki/tls/certs cp ca.key /etc/pki/tls/private/ca.key cp ca.csr /etc/pki/tls/private/ca.csr

vi +/SSLCertificateFile /etc/httpd/conf.d/ssl.conf

[...] SSLCertificateFile /etc/pki/tls/certs/ca.crt [...] SSLCertificateKeyFile /etc/pki/tls/private/ca.key [...]

/etc/init.d/httpd restart

Go to the default SSL web site’s URL (e.g. https://www.example.com) and test if it works (I’m using the default self-signed certificate here, that’s why I have a certificate warning, but this has no effect on using SPDY):

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

2 Installing mod_spdy

First make sure at is installed:

yum install at

Google provides Fedora/CentOS packages for mod_spdy on https://developers.google.com/speed/spdy/mod_spdy/. Simply download the correct one for your architecture (32- or 64-bit) to your server…

64-bit:

cd /tmp wget https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_x86_64.rpm

32-bit:

cd /tmp wget https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_i386.rpm

… and install it as follows:

rpm -U mod-spdy-*.rpm

Restart Apache afterwards:

/etc/init.d/httpd restart

The good thing is, mod_spdy needs no configuration, it works out of the box!

(In fact, there is a configuration file, /etc/httpd/conf.d/spdy.conf, but the default settings should be ok.

cat /etc/httpd/conf.d/spdy.conf

LoadModule spdy_module /usr/lib64/httpd/modules/mod_spdy.so <IfModule spdy_module> # Turn on mod_spdy. To completely disable mod_spdy, you can set # this to "off". SpdyEnabled on # In order to support concurrent multiplexing of requests over a # single connection, mod_spdy maintains its own thread pool in # each Apache child process for processing requests. The default # size of this thread pool is very conservative; you can override # it with a larger value (as below) to increase concurrency, at # the possible cost of increased memory usage. # #SpdyMaxThreadsPerProcess 30 # Memory usage can also be affected by the maximum number of # simultaneously open SPDY streams permitted for each client # connection. Ideally, this limit should be set as high as # possible, but you can tweak it as necessary to limit memory # consumption. # #SpdyMaxStreamsPerConnection 100 </IfModule>

You can learn more about the configuration options on https://developers.google.com/speed/spdy/mod_spdy/install.

)

3 Testing

Now let’s test if SPDY is working. We need a browser with SPDY support. e.g. Google Chrome. Open Chrome and reload your SSL web site (e.g. https://www.example.com) – it is important that you reload it so that it can use SPDY (the first time you loaded it in chapter 1 it used normal HTTPS). Afterwards, open a new tab and type in the URL

chrome://net-internals/#spdy

If everything went well, your SSL vhost should now be listed in the table which means SPDY support is working.

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

(Because of SPDY’s fallback mechanism to HTTPS, your SSL vhost will still work in any other browser that does not support SPDY.)

4 Links

New Post has been published on http://mocco.sk/using-mod_spdy-with-apache2-on-centos-6-3/

Using mod_spdy With Apache2 On CentOS 6.3

Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Follow me on Twitter Last edited 03/04/2013

SPDY (pronounced “SPeeDY”) is a new networking protocol whose goal is to speed up the web. It is Google’s alternative to the HTTP protocol and a candidate for HTTP/2.0. SPDY augments HTTP with several speed-related features such as

stream multiplexing and header compression. To use SPDY, you need a web server and a browser (like Google Chrome and upcoming versions of Firefox) that both support SPDY. mod_spdy is an open-source Apache module that adds support for the SPDY protocol to the Apache HTTPD server. This tutorial explains how to use mod_spdy with Apache2 on CentOS 6.3.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

SPDY runs over HTTPS, so we need an HTTPS-enabled web site to test SPDY. Please note that SPDY will fall back to HTTPS if the user’s browser does not support SPDY or if things go wrong, so installing mod_spdy doesn’t hurt your existing setup.

I’m assuming that you have a working LAMP setup, as described on Installing Apache2 With PHP5 And MySQL Support On CentOS 6.3 (LAMP).

For testing purposes I will simply use the default SSL web site that comes with the Apache package on CentOS (you don’t need to do this if you already have an SSL web site on your server). If you have no SSL web site, you can enable the default SSL web site as follows:

yum install mod_ssl openssl

openssl genrsa -out ca.key 4096

openssl req -new -key ca.key -out ca.csr

openssl x509 -req -days 365 -in ca.csr -signkey ca.key -out ca.crt

cp ca.crt /etc/pki/tls/certs cp ca.key /etc/pki/tls/private/ca.key cp ca.csr /etc/pki/tls/private/ca.csr

vi +/SSLCertificateFile /etc/httpd/conf.d/ssl.conf

[...] SSLCertificateFile /etc/pki/tls/certs/ca.crt [...] SSLCertificateKeyFile /etc/pki/tls/private/ca.key [...]

/etc/init.d/httpd restart

Go to the default SSL web site’s URL (e.g. https://www.example.com) and test if it works (I’m using the default self-signed certificate here, that’s why I have a certificate warning, but this has no effect on using SPDY):

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

2 Installing mod_spdy

First make sure at is installed:

yum install at

Google provides Fedora/CentOS packages for mod_spdy on https://developers.google.com/speed/spdy/mod_spdy/. Simply download the correct one for your architecture (32- or 64-bit) to your server…

64-bit:

cd /tmp wget https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_x86_64.rpm

32-bit:

cd /tmp wget https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_i386.rpm

… and install it as follows:

rpm -U mod-spdy-*.rpm

Restart Apache afterwards:

/etc/init.d/httpd restart

The good thing is, mod_spdy needs no configuration, it works out of the box!

(In fact, there is a configuration file, /etc/httpd/conf.d/spdy.conf, but the default settings should be ok.

cat /etc/httpd/conf.d/spdy.conf

LoadModule spdy_module /usr/lib64/httpd/modules/mod_spdy.so <IfModule spdy_module> # Turn on mod_spdy. To completely disable mod_spdy, you can set # this to "off". SpdyEnabled on # In order to support concurrent multiplexing of requests over a # single connection, mod_spdy maintains its own thread pool in # each Apache child process for processing requests. The default # size of this thread pool is very conservative; you can override # it with a larger value (as below) to increase concurrency, at # the possible cost of increased memory usage. # #SpdyMaxThreadsPerProcess 30 # Memory usage can also be affected by the maximum number of # simultaneously open SPDY streams permitted for each client # connection. Ideally, this limit should be set as high as # possible, but you can tweak it as necessary to limit memory # consumption. # #SpdyMaxStreamsPerConnection 100 </IfModule>

You can learn more about the configuration options on https://developers.google.com/speed/spdy/mod_spdy/install.

)

3 Testing

Now let’s test if SPDY is working. We need a browser with SPDY support. e.g. Google Chrome. Open Chrome and reload your SSL web site (e.g. https://www.example.com) – it is important that you reload it so that it can use SPDY (the first time you loaded it in chapter 1 it used normal HTTPS). Afterwards, open a new tab and type in the URL

chrome://net-internals/#spdy

If everything went well, your SSL vhost should now be listed in the table which means SPDY support is working.

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

(Because of SPDY’s fallback mechanism to HTTPS, your SSL vhost will still work in any other browser that does not support SPDY.)

4 Links

New Post has been published on http://mocco.sk/using-mod_spdy-with-apache2-on-scientific-linux-6-3/

Using mod_spdy With Apache2 On Scientific Linux 6.3

Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Follow me on Twitter Last edited 02/27/2013

SPDY (pronounced “SPeeDY”) is a new networking protocol whose goal is to speed up the web. It is Google’s alternative to the HTTP protocol and a candidate for HTTP/2.0. SPDY augments HTTP with several speed-related features such as

stream multiplexing and header compression. To use SPDY, you need a web server and a browser (like Google Chrome and upcoming versions of Firefox) that both support SPDY. mod_spdy is an open-source Apache module that adds support for the SPDY protocol to the Apache HTTPD server. This tutorial explains how to use mod_spdy with Apache2 on Scientific Linux 6.3.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

SPDY runs over HTTPS, so we need an HTTPS-enabled web site to test SPDY. Please note that SPDY will fall back to HTTPS if the user’s browser does not support SPDY or if things go wrong, so installing mod_spdy doesn’t hurt your existing setup.

I’m assuming that you have a working LAMP setup, as described on Installing Apache2 With PHP5 And MySQL Support On Scientific Linux 6.3 (LAMP).

For testing purposes I will simply use the default SSL web site that comes with the Apache package on Scientific Linux (you don’t need to do this if you already have an SSL web site on your server). If you have no SSL web site, you can enable the default SSL web site as follows:

yum install mod_ssl openssl

openssl genrsa -out ca.key 4096

openssl req -new -key ca.key -out ca.csr

openssl x509 -req -days 365 -in ca.csr -signkey ca.key -out ca.crt

cp ca.crt /etc/pki/tls/certs cp ca.key /etc/pki/tls/private/ca.key cp ca.csr /etc/pki/tls/private/ca.csr

vi +/SSLCertificateFile /etc/httpd/conf.d/ssl.conf

[...] SSLCertificateFile /etc/pki/tls/certs/ca.crt [...] SSLCertificateKeyFile /etc/pki/tls/private/ca.key [...]

/etc/init.d/httpd restart

Go to the default SSL web site’s URL (e.g. https://www.example.com) and test if it works (I’m using the default self-signed certificate here, that’s why I have a certificate warning, but this has no effect on using SPDY):

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

2 Installing mod_spdy

First make sure at is installed:

yum install at

Google provides Fedora/CentOS/Scientific Linux packages for mod_spdy on https://developers.google.com/speed/spdy/mod_spdy/. Simply download the correct one for your architecture (32- or 64-bit) to your server…

64-bit:

cd /tmp wget https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_x86_64.rpm

32-bit:

cd /tmp wget https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_i386.rpm

… and install it as follows:

rpm -U mod-spdy-*.rpm

Restart Apache afterwards:

/etc/init.d/httpd restart

The good thing is, mod_spdy needs no configuration, it works out of the box!

(In fact, there is a configuration file, /etc/httpd/conf.d/spdy.conf, but the default settings should be ok.

cat /etc/httpd/conf.d/spdy.conf

LoadModule spdy_module /usr/lib64/httpd/modules/mod_spdy.so <IfModule spdy_module> # Turn on mod_spdy. To completely disable mod_spdy, you can set # this to "off". SpdyEnabled on # In order to support concurrent multiplexing of requests over a # single connection, mod_spdy maintains its own thread pool in # each Apache child process for processing requests. The default # size of this thread pool is very conservative; you can override # it with a larger value (as below) to increase concurrency, at # the possible cost of increased memory usage. # #SpdyMaxThreadsPerProcess 30 # Memory usage can also be affected by the maximum number of # simultaneously open SPDY streams permitted for each client # connection. Ideally, this limit should be set as high as # possible, but you can tweak it as necessary to limit memory # consumption. # #SpdyMaxStreamsPerConnection 100 </IfModule>

You can learn more about the configuration options on https://developers.google.com/speed/spdy/mod_spdy/install.

)

3 Testing

Now let’s test if SPDY is working. We need a browser with SPDY support. e.g. Google Chrome. Open Chrome and reload your SSL web site (e.g. https://www.example.com) – it is important that you reload it so that it can use SPDY (the first time you loaded it in chapter 1 it used normal HTTPS). Afterwards, open a new tab and type in the URL

chrome://net-internals/#spdy

If everything went well, your SSL vhost should now be listed in the table which means SPDY support is working.

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

(Because of SPDY’s fallback mechanism to HTTPS, your SSL vhost will still work in any other browser that does not support SPDY.)

4 Links

mod-less is LESS apache2 module :

This apache2 module is written to compile LESS code inside the css files when they are requested so the process will be transparent from any script using css no matter what it's language is

this apache2 module is written using c.

How it works :

when a request is sent to any css file this request will be handeled by this module, the module will compile the css file and create another file from this css file with .less extension, then the module will pass the compiled version as a resposne to the request

example:

request: http://localhost/themes/css/style.css <=== this css file containes LESS codes insde it the module will compile style.css and save the compiled version to : resposne: http://localhost/themes/css/style.css.less <==== this is the compiled version from style.css then the moduel will return the compiled version as response for the file "style.css"

Dependencies :

Apache2 sudo apt-get install apache2 Less Css sudo apt-get install rubygems1.8 sudo gem install rubygems-update sudo update_rubygems sudo gem install less

Installation :

download the project from here

https://github.com/waleedq/libapache2-mod-less_beta1/tarball/master

copy /bin/mod_less.so to /usr/lib/apache2/modules/mod_less.so chmod 644 /usr/lib/apache2/modules/mod_less.so copy /bin/less.load to /etc/apache2/mods-available/less.load copy /bin/less.conf to /etc/apache2/mods-available/less.conf

you can edit the less.conf file to change when this module is gonna be invoked

for example : this conf with "\.css$" will invoke the module when any .css file is requested <FilesMatch "\.css$"> SetHandler less </FilesMatch> changing "\.css$" to "\.less$" will invoke the module only for requested files with .less extension

Compile from source :

you can clone the code from

git://github.com/waleedq/libapache2-mod-less_beta1.git

github repo link:

https://github.com/waleedq/libapache2-mod-less_beta1

source can be found in /src/mod_less.c to compile it you will need the apxs2 tool which can be found in the apache2-prefork-dev package

sudo apt-get install apache2-prefork-dev

after installing apxs2 tool, cd to the src directory and execute this command

sudo apxs2 -c -i mod_less.c

compiled file "mod_less.so" will be automatically copied to /usr/lib/apache2/modules/mod_less.so and chmoded. you only need to add the less.load and less.conf as mentioned in the Installation section above.

Developers :

waleed al qadi (waleedq).