Below set of steps involve setting up Tomcat 6 on CentOS 5 with Java 1.6
Download Apache Tomcat
$ wget http://apache.parentingamerica.com/tomcat/tomcat-6/v6.0.36/bin/apache-tomcat-6.0.36.tar.gz
Go to opt/ folder and extract Tomcat
$ cd /opt
$ tar -xzf apache-tomcat-6.0.36.tar.gz
Create a tomcat user
$ useradd -d /opt/apache-tomcat-6.0.36/ tomcatuser
Change user permission on tomcat folder
$ chown -R tomcatuser:tomcatuser apache-tomcat-6.0.36
(more…)
Add the following list of lines into .htaccess file or to vhost configuration file appropriate to the folder within the website
<Directory /securedata>
Order Deny,Allow
Deny from all
</Directory>
Same will be the case for denying files within directories
<Files ~ “\.ini$”>
Order allow,deny
Deny from all
</Files>
The above lines of code will be helpful for us to prevent .svn files, .ini files, .htaccess files, include files from display within Apache
Follow the simple steps given below to integrate Zend framework with other applications like WordPress, Joomla and other such open source or custom web applications.
i) Setup your Zend framework application as usual.
ii) Set the document root of the Zend application to the public folder within Zend install
iii) Now setup a folder for your wordpress or joomla or custom application. Let us assume that we want to create a custom blog application. Create a folder “blog” within “public” folder. Inside blog folder, create two files – .htaccess and index.php. Code for the two files are given below
(more…)
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. (more…)
… 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.
(more…)
Apache server documentation provides us clear set of steps to do name/IP based virtual hosting which is stated in the below URL
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
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.
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. (more…)
Download the latest version of Zend framework from
http://framework.zend.com/download/latest
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
(more…)
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:
Copyright ©2008 - 2013. Kurinchilion Inc.
