After configuring Apache server settings on the name server, you may encounter a message “[warn] NameVirtualHost 192.168.1.3:80 has no VirtualHosts”

The issue may be due to more than one entry of NameVirtualHost lines in the configuration settings. You can find this out by

$ grep NameVirtual * -R
site1:NameVirtualHost *:80
site2:NameVirtualHost *:80

Linux Solution: Remove one of the occurance of the NameVirtualHost and the warning message that you receive will vanish.

http://httpd.apache.org/docs/2.0/vhosts/examples.html

- Running several name-based web sites on a single IP address.
- Name-based hosts on more than one IP address.
- Serving the same content on different IP addresses
- Running different sites on different ports
- IP-based virtual hosting
- Mixed port-based and ip-based virtual hosts
- Mixed name-based and IP-based vhosts
- Using Virtual_host and mod_proxy together
- Migrating a name-based vhost to an IP-based vhost

- Using the ServerPath directive

Solution:

Search for the apache configuration file (httpd.conf or vhosts.conf if you have configured a virtual host). Check for the directory permission set for the document root of the web site in question and do the following changes.

<Directory /path/to/web/root >
Options IndexesFollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>

Change this to

<Directory /path/to/web/root >
Options IndexesFollowSymLinks
AllowOverride None
Order allow, deny
Allow from all
</Directory>

Restart apache web server to ensure that the effect of the settings take place.

At the time of writing it was 1.10.2 available at Zend 1.10.2

$ pwd
/tmp

$ wget http://framework.zend.com/releases/ZendFramework-1.10.2/ZendFramework-1.10.2.tar.gz

$ mkdir /opt/zendframework
$ tar -C /opt/zendframework -zxvf ZendFramework-1.10.2.tar.gz
$ cd /opt/zendframework

Create a symbolic link to the downloaded zend framework release in order to help ease maintaining different releases

$ ln -s ZendFramework-1.10.2.tar.gz currentzend

Edit php.ini to include the path to the symbolic link created for zend release

$ vi /etc/php5/apache2/php.ini

; UNIX: “/path1:/path2″
include_path = “.:/opt/zendframework/currentzend”

In order to do command line execution in zend, we need to set up the PHP CLI by again editing php.ini for the cli

$ vi /etc/php5/cli/php.ini
; UNIX: “/path1:/path2″
include_path = “.:/opt/zendframework/currentzend”

For all users, set the path to Zend’s bin directory
$ vi ~/.bashrc

and add the line
PATH=$PATH:/opt/zendframework/currentzend/bin

Restart apache for the changes to take effect
$ /etc/init.d/apache2 restart

To check if the changes take place as expected, type
$ zf.sh show version
and you should get
Zend Framework Version 1.10.2

Now, we move into setting up Zend framework

$ cd /var/www
$ zf.sh create project myzend

This will set up the MVC zend structure. Copy the Zend folder into your new project “myzend”

$ cp -r /opt/zendframework/currentzend/library/Zend /var/www/myzend/library/Zend

Now go to your project to test if the installation was successful by typing
http://localhost/myzend/public/

This should open up the welcome page to zend framework.

“Servers should be cautious about depending on URI lengths above 255 bytes because some older client or proxy implementations may not properly support these lengths.”

Different browser agents support different URI length acceptance. In addition, servers too play a role in accepting/denying URI’s over certain length which may either truncate the URI or may give lengthy URI message indications.

It is always advisable to rely on shorter URI’s and to post data when more field sets are to be transferred across web pages.

POST data too has its limit. In this case, it is the size of the data which is controlled by the server settings.

Some interesting discussions:

Limit on query string GET URL parameters

Once you finish generating the CSR file, you need to paste the content of the CSR file on to the SSL certificate request page in order for the certificate authorities to start their verification process.

Command line prompts in a Linux box

Find where openssl is installed and navigated to that directory
$ whereis openssl

Mostly it will be at /usr/bin/. If it is in a different path, then navigate to that directory path
$ cd /usr/bin

If asked for a pass phrase, enter a phrase which you need to use when generating the CSR file from the key file.

Next, we will use des3 algorithm to generate the key. If you want to generate a key for a site abc.com you can give certificate-name=www.abc.com for easy reference
$ openssl genrsa -des3 -out certificate-name.key 2048

Next in the process is to generate the CSR file from the key
$ openssl req -new -key certificate-name.key -out certificate-name.csr

This will involve a step of questions where you need to answer your two-digit country code, province or state, company name, organizational unit name, company name and email address.For the part that involves “Common Name (eg, your name or your server’s name)” enter the domain name for which you want to get the certificate (for e.g. www.abc.com).

Now, copy the content of CSR file and paste it on the certificate request page (probably the web page of the certificate authorities web page like RapidSSL, GoDaddy, VeriSign, Thawte SSL certificate issuance authority.

After submitting the .csr file, you need to wait for the .cer files from the certificate authority. If you are going with Godaddy, they will send you a bundle certificate along with the original .cer file which you need to install in your web server.

Check the error log file (in ubuntu it is in /var/log/apache2/error.log) for the above stated error message. Check the .htaccess file or the apache configuration files where you have restricted file permission using File Directive.

Premature end of script headers
500 Internal Server Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers.

Some troubleshooting tips:

i) Check /var/log/apache2/error.log (in ubuntu, check the respective apache error log location for the messages)

ii) Check if the content type of the page is correctly set for the html content output.

print “Content-type: text/html\n\n”;

iii) Check if a valid permission has been given for the file to get executed. The file need permission 755 for it to be executed on the server.

iv) Check if the configuration path, inclusion path are set correctly in the referenced programs

Check the apache configuration settings

i) The first is the reference to folder where cgi or perl files will reside and its execute permission settings

 <ScriptAlias /cgi-bin/ /usr/local/cgi-bin/>
 <Directory "/usr/local/cgi-bin">
     AllowOverride None
     Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
     Order allow,deny
     Allow from all
 </Directory>

ii) The second is the proper add handlers that are set for the file execution

AddHandler cgi-script .cgi .pl
<Files ~ "\.pl$">
    Options +ExecCGI
</Files>
<Files ~ "\.cgi$">
   Options +ExecCGI
</Files>

Check the apache error log for any messages (/var/log/apache2/error.log).

By default, Apache displays the version of the server, modules loaded in the server and the version of PHP if PHP is configured with Apache.

In httpd.conf file, set the following directives.

ServerSignature Off
ServerTokens ProductOnly

By default, ServerSignature is set to Off and ServerTokens is set to Full in most Linux distros.