First, download the Zend framework and unzip the file contents to a location. At the time of the writing ZendFramework-1.11.12 was in use and we have used that version in this example. Key content of the download is the /library folder which has Zend libraries in it.
Then, go to the “conf” folder that was created when the site was created.
Inside the conf folder, create a new file and name it vhost.conf
Add the below contents to vhost.conf and save it. Continue Reading…
… a question that raises in the mind of programmers developing applications in their local development environments.
This can be achieved by making the following modifications.
Step (i) Install the WAMP / XAMPP server in your windows machine. After this install you will be able to access sites created on the localhost with URL http://localhost
Step (ii) Download and extract the send mail application for Windows from http://glob.com.au/sendmail/. Remember the path where you have extracted sendmail. For e.g. c:\wamp\sendmail
Step (iii) Edit sendmail.ini within c:\wamp\sendmail. This ini file has enough documentation explaining how the configuration changes should happen on the file.
Apache server documentation provides us clear set of steps to do name/IP based virtual hosting which is stated in the below URL
– 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
Apache Error log shows the message “Client denied by server configuration” and the user sees “Forbidden Access” when they try to visit a web page.
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. Continue Reading…
RFC 2616 – Section 3 states:
“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:
In order to install SSL certificates on your Apache server you need to generate a key pair and a CSR (certificate signing request) as the first step. The following points will guide you in the creation of CSR file.
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
Apache Error Log Expected “</File> but saw </Files>”
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.
Apache errors and the approach to solve it
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