<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<HTML> 
  <HEAD> <BASE TARGET="_top"> 
	 <TITLE>HTTP Error 500 Internal server error Explained</TITLE>
	 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
	 <META CONTENT="en" HTTP-EQUIV="Content-Language"> 
  </HEAD> 
  <BODY BGCOLOR="#ffffff"> <BR>
<!--TEXTSTART-->
	 <TABLE WIDTH="95%" BORDER="0" CELLSPACING="0" CELLPADDING="0"
	  ALIGN="CENTER"> 
		<TR> 
		  <TD VALIGN="TOP"> 
			 <P ALIGN="CENTER"><h1>HTTP Error 500 Internal server error</h1></P> 
			 <P><B>Introduction</B></P> 
			 <BLOCKQUOTE> 
				<P>The Web server (running the Web Site) encountered an unexpected
				  condition that prevented it from fulfilling the request by the client (e.g.
				  your Web browser or our CheckUpDown robot) for access to the requested URL.</P>
				
				<P>This is a 'catch-all' error generated by the Web server.
				  Basically something has gone wrong, but the server can not be more specific
				  about the error condition in its response to the client. In addition to the 500
				  error notified back to the client, the Web server should generate some kind of
				  internal error log which gives more details of what went wrong. It is up to the
				  operators of the Web server site to locate and analyse these logs. </P>
				</BLOCKQUOTE> 
			 <P><B>500 errors in the HTTP cycle</B></P> 
			 <BLOCKQUOTE> 
				<P>Any client (e.g. your Web browser or our CheckUpDown robot) goes
				  through the following cycle when it communicates with the Web server:</P> 
				<UL> 
				  <LI>Obtain an IP address from the IP name of the site (the site
					 URL without the leading 'http://'). This lookup (conversion of IP name to IP
					 address) is provided by domain name servers (DNSs). </LI> 
				  <LI>Open an IP socket connection to that IP address. </LI> 
				  <LI>Write an HTTP data stream through that socket. </LI> 
				  <LI>Receive an HTTP data stream back from the Web server in
					 response. This data stream contains status codes whose values are determined by
					 the HTTP protocol. Parse this data stream for status codes and other useful
					 information. </LI> 
				</UL> 
				<P>This error occurs in the final step above when the client
				  receives an HTTP status code that it recognises as '500'.</P> </BLOCKQUOTE> 
			 <P><B>Fixing 500 errors - general</B></P> 
			 <BLOCKQUOTE> 
				<P>This error can only be resolved by fixes to the Web server
				  software. It is not a client-side problem. It is up to the operators of the Web
				  server site to locate and analyse the logs which should give further
				  information about the error.</P> </BLOCKQUOTE> 
			 <P><B>Fixing 500 errors - CheckUpDown</B></P> 
			 <BLOCKQUOTE> 
				<P>Please contact us (email preferred) whenever you encounter 500
				  errors on your CheckUpDown account. We then have to liaise with your ISP and
				  the vendor of the Web server software so they can trace the exact reason for
				  the error. Correcting the error may require recoding program logic for the Web
				  server software, which could take some time. </P> </BLOCKQUOTE> </TD>
<!--TEXTEND-->
		</TR> 
	 </TABLE>
 <BR> </BODY>
</HTML>