|
Home
Web Hosting Guide
Compare Hosting Plans
Basic Hosting Plan
Professional Hosting Plan
Extreme Hosting Plan
Email Only Hosting
Web Forwarding
Advanced Features
Hosting Control Panel
SSL Certificates
Hosting Order Page
WISDOM
The Essence of Knowledge is Having it to Apply it. |
Full Local Path
How To Use relative paths in your Perl scripts Set-Cookie Header is ignored when combined with Location Header File upload problems via HTTP Changing the PHP timeout value Problems sending email from scripts Using the ASPjpeg Component Using the ASPupload Component Using the ASPemail Component Using the ASPemail .NET wrapper Using the CDONTS Component Using the CDOSYS Component in ASP.NET (C#)
Some scripts require the local system path for files referenced in the
script.
example: c:/websites/webhostdirectory/domain.com You can find the local system path by using the Web Based FTP utility. From your Hosting Control Panel: 1) Select Web Site/Domain Management -> Domain.com -> Web Based FTP. 2) After the utility loads, you can "Toggle local/remote path" on the top right portion of the screen.
When specifying a full local path in a Perl script you must use only single
forward slashes as
follows:
C:/Websites/webhostdirectory/yourdomain.com/cgi-bin You cannot use single backslashes or double forward slashes.
You cannot print a "Location" header combined with a "Set-Cookie" in IIS with
default header processing settings. If this is done, IIS ignores it and just
does the redirect. To avoid this, you must disable IIS header processing by
appending "nph-" to the front of the filename and print out the HTTP header
along with the cookie and location. Please refer to the following Microsoft
Knowledgebase article for more
information:
http://support.microsoft.com/default.aspx?scid=kb;en-us;176113
When attempting to transfer large files over 1-2MB in size via HTTP, you will
probably run into timeout problems. All scripting languages have a timeout set
in our system. For example, PHP is set to 90 seconds and Perl is set to 300
seconds. When you post form data to a script (form data can contain files to
upload), all of the data must be sent and received by the server before the
script can start executing. Unfortunately, this time is counted as script
execution time and is subject to the global timeout.
Normally, form data is very small in size and usually only contains contact information or a short message and can be uploaded in a matter of seconds, but if the form data contains files, the upload time increases. The amount of time it takes to upload this form data is based on the speed of the client -> server connection. On a broadband connection, you can safely say a 1-2MB file upload will upload without any problems. On a dialup connection, you will begin to encounter problems as your file size approaches 1MB. While it is possible to change this timeout setting in PHP, HTTP is generally very unstable for large file transfer because of its connectionless nature. You cannot be guaranteed that your transfer will complete. We do not recommend and will not support the transfer of large files via HTTP unless you are using a file upload component such as AspUpload which operates in a manner that bypasses server timeout problems. ASPUpload will not fail on large file transfers. Another option is to utilize FTP which is a connection based protocol and can recover from errors encountered during the upload process.
All of our Web Servers have a global value of 90 seconds for the PHP timeout.
You may need to increase this for a file upload script or another script that
needs a long execution time. To do this, change the PHP timeout variable using
the ini_set function at the top of your script. The following code
snippet is an example of how to update the timeout
variable:
ini_set("max_execution_time","90") Further PHP documentation on this function can be found here: http://us2.php.net/manual/en/function.ini-set.php We do have a Global setting on the servers that allows a maximum time of 5 minutes to any PHP process.
If your script is returning an error when sending email or the email is not
being received, the following reasons could be the problem:
1. The email address you are sending from may not be created in our mail server. If you are using our SMTP server to send mail from your scripts and you are specifying a FROM address from a domain that is hosted on our system, that address must exist and needs to be different from the To address . If it does not exist, you can create it by logging into our Control Panel, then going to Web Site / Domain Management -> Email Accounts. 2. The email address you are sending to may not be valid. If your domain is hosted on our system, you can check to see if the email address is valid by logging into our Control Panel, then going to Web Site / Domain Management -> Email Accounts or Email Forwards. Many times there can be confusion with this if your domain is in the transfer process or you have recently changed your name servers. If you have verified that both email addresses are valid, please contact support for further assistance. |
||||||||