How to enable mssql support on Linux server ?

Ans : You need to first compile freetds and then compile PHP with freetds support.

What is FreeTDS?

FreeTDS is a free implementation of the TDS (Tabular Data Stream) protocol that is used by Sybase and Microsoft for their database products. It implements TDS 4.2, 5.0, 7.0 and 8.0, and can communicate with any Sybase or Microsoft SQL Server.

FreeTDS comes with a low level library (the TDS layer) along with a number of APIs (Application Programming Interfaces). The APIs are DB-Lib, CT-Lib, and ODBC.

You can install freetds by using yum.

yum install freetds

After that you need to recompile the php with mssql support

check the php  version on the server and then download the same php version file for example php 5.3.2.

You can downlad php version by using this URL  http://us3.php.net/downloads.php

cd /usr/local/src

wget http://us3.php.net/get/php-5.3.2.tar.bz2/from/in.php.net/mirror

tar  -xzvf php-5.3.2.tar.bz2

cd  php-5.3.2/ext/mssql

phpize
./configure –with-mssql
make
make install

Next look for the mssql.so file and make sure it is in the module directory specified in your php.ini. Copy it to the specified location if needed.

php -i | grep php.ini

vi /usr/local/lib/php.ini

Add this line to your php.ini:

extension=mssql.so

Save the php.ini and restart Apache:

/etc/init.d/httpd restart

Done

Error : Curl webservice CURLE_SSL_CACERT (60) Peer certificate cannot be authenticated with known CA certificates.

Solution:  Add the following line in your file on which you have access the domain.

curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);

Done

There was a problem importing the database. The following error had occured:

1071: Specified key was too long; max key length is 1000 bytes;

http://forums.oscommerce.com/topic/331202-1071-specified-key-was-too-long-max-key-length-is-1000-bytes-create-table/

What is Web Hosting?

Web hosting is a service that allows organizations and individuals to post a website or web page on to the Internet. A web host, or web hosting service provider, is a business that provides the technologies and services needed for the website or webpage to be viewed in the Internet. Websites are hosted, or stored, on special computers called servers.

When Internet users want to view your website, all they need to do is type your website address into their browser. Their computer will then connect to your server and your webpages will be delivered to them through the browser.

Most hosting companies require that you own your domain name in order to host with them. If you do not have a domain name, the hosting companies will help you purchase one.

How to find the domain name (DNS) information.

http://network-tools.com or http://xwhois.com

http://intodns.com/

http://centralops.net/co/

http://www.dnsstuff.com/

http://www.ipmango.com/megadns.php

http://www.dnswatch.info

ModSecurity installation requirements:

1) ModSecurity 2.x works only with Apache 2.0.x or higher. Version 2.2.x is highly recommended.

2.Make sure you have mod_unique_id installed.

mod_unique_id is packaged with Apache httpd.

3.libapr and libapr-util

http://apr.apache.org/

4.

libpcre

http://www.pcre.org/

5.

libxml2

http://xmlsoft.org/downloads.html

6.

liblua v5.1.x

This library is optional and only needed if you will be using the new Lua engine.

http://www.lua.org/download.html

Note that ModSecurity requires the dynamic libraries. These are not built by default in the source distribution, so the binary distribution is recommended.
7.

libcurl v7.15.1 or higher

If you will be using the ModSecurity Log Collector (mlogc) to send audit logs to a central repository, then you will also need the curl library.

http://curl.haxx.se/libcurl/

Note

Many have had issues with libcurl linked with the GnuTLS library for SSL/TLS support. It is recommended that the openssl library be used for SSL/TLS support in libcurl.

ModSecurity installation consists of the following steps:

1.

Stop Apache httpd
2.

Unpack the ModSecurity archive
3.

Building differs for UNIX (or UNIX-like) operating systems and Windows.
*

UNIX
1.

Run the configure script to generate a Makefile. Typically no options are needed.

./configure

Options are available for more customization (use ./configure –help for a full list), but typically you will only need to specify the location of the apxs command installed by Apache httpd with the –with-apxs option.

./configure –with-apxs=/path/to/httpd-2.x.y/bin/apxs
Note

There are certain configure options that are meant for debugging an other development use. If enabled, these options can substantially impact performance. These options include all –debug-* options as well as the –enable-performance-measurements options.
2.

Compile with: make
3.

Optionally test with: make test
Note

This is step is still a bit experimental. If you have problems, please send the full output and error from the build to the support list. Most common issues are related to not finding the required headers and/or libraries.
4.

Optionally build the ModSecurity Log Collector with: make mlogc
5.

Optionally install mlogc: Review the INSTALL file included in the apache2/mlogc-src directory in the distribution.
6.

Install the ModSecurity module with: make install
*

Windows (MS VC++
1.

Edit Makefile.win to configure the Apache base and library paths.
2.

Compile with: nmake -f Makefile.win
3.

Install the ModSecurity module with: nmake -f Makefile.win install
4.

Copy the libxml2.dll and lua5.1.dll to the Apache bin directory. Alternatively you can follow the step below for using LoadFile to load these libraries.
4.

Edit the main Apache httpd config file (usually httpd.conf)

On UNIX (and Windows if you did not copy the DLLs as stated above) you must load libxml2 and lua5.1 before ModSecurity with something like this:

LoadFile /usr/lib/libxml2.so
LoadFile /usr/lib/liblua5.1.so

Load the ModSecurity module with:

LoadModule security2_module modules/mod_security2.so

5.

Configure ModSecurity
6.

Start Apache httpd
7.

You should now have ModSecurity 2.x up and running.

How to check gzip compression is enable on the server or domain.

The gzip compression required mod_gzip.c or mod_deflate.c module installed on the server.

How you can check this module installed on  the server

root@server [~]# /usr/local/apache/bin/httpd -l

or

root@server [~]# httpd -l

If one of the module is installed on the server then, you can enable the gzip compression for the account as follows.

You can check it by using the following commands

You need to add the following code into the .htaccess file to enable the gzip compression for the domain.

After adding above code in .htaccess file, you can check the gzip compression is enable or not by using the following URL.

http://www.gidnetwork.com/tools/gzip-test.php

When you enter the domain name in the above URL then it shows the

Web page compressed? Yes
Compression type? gzip

When using cPanel the way to enable allow_url_include directive locally (per user) is to create an Virtual Host include:

First create an include file:
/usr/local/apache/conf/userdata/std/2/username/domain.com/custom.conf

Add directive to custom.conf:

php_admin_flag allow_url_include On


Then run to enable include:
/scripts/ensure_vhost_includes --user=username --verbose

Alternatively, enabling allow_url_include globally (server-wide) is done by editing /usr/local/lib/php.ini and adding “allow_url_include = On” directive to the Fopen wrapper section.
;;;;;;;;;;;;;;;;;;
; Fopen wrappers ;
;;;;;;;;;;;;;;;;;;/code>

; Whether to allow the treatment of URLs (like http:// or ftp://) as files.
allow_url_fopen = On
allow_url_include = On

and restarting apache by issuing “service httpd restart” command as root.

Welcome to bestdesigns.co.in/blog.  We will try to provide most important inforamtion about the webhosting related problems with the solution.