<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>2Checkout.com &#187; server</title>
	<atom:link href="http://www.2checkout.com/blog/tag/server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.2checkout.com</link>
	<description>merchant account / credit card processing alternative</description>
	<lastBuildDate>Thu, 09 Feb 2012 15:02:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Why do I get an HTTP Error 500 (Internal Server Error) on Passback?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-500-internal-server-error-on-passback/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-500-internal-server-error-on-passback/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[server]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/why-do-i-get-an-http-error-500-internal-server-error-on-passback/</guid>
		<description><![CDATA[An HTTP Error 500 (Internal Server Error) indicates that there is a problem inside of your script or the servers configuration. This error is most likely caused by a typo in the code or an invalid or illegal use of a function within the script. For the pass back to function correctly, then your script [...]]]></description>
			<content:encoded><![CDATA[<p>An HTTP Error 500 (Internal Server Error) indicates that there is a problem inside of your script or the servers configuration. This error is most likely caused by a typo in the code or an invalid or illegal use of a function within the script. For the pass back to function correctly, then your script must be correctly set up.</p>
<p>HTTP errors are not generated specifically by 2Checkout. They are a part of the HTTP protocol and are common amongst all web servers. It is therefore beyond the realm of 2Checkout&#8217;s support to provide you with specific instructions for making these changes as every server is set up differently and 2CO does not provide server administration services as part of our support plan.</p>
<p>For assistance with debugging your scripts, we suggest that you contact your server&#8217;s administrator, webmaster, or hosting provider&#8217;s technical support staff. </p>
<p>We have observed that this error is experienced in certain web browsers more than in others, in particular within Internet Explorer. If your return page or script does not output at least 530 characters, this can potentially cause a MIME header error. Mozilla based browsers such as Firefox seem to be able to handle these pages and will display either the real error or the small output when Internet Explorer has problems. Since this issue is an issue with the browser software itself, there is little 2Checkout can do to control this. If you are receiving this error, please try to increase the output that your return page generates to more than 530 characters or try a different web browser to see if you observe different results. Note that this is not a solution for all HTTP 500 error messages, but it is meant to be a useful step in debugging your script and has been reported as a successful step by some of our other users.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-500-internal-server-error-on-passback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why do I get an HTTP Error 405 on Passback?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-405-on-passback/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-405-on-passback/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return]]></category>
		<category><![CDATA[server]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/why-do-i-get-an-http-error-405-on-passback/</guid>
		<description><![CDATA[This is a problem with your script and/or your web server. The error means that you are attempting to pass back to a file does not have the necessary permissions on the server to receive Post information from another script. If you have administrative or root access to your server, be sure that this file [...]]]></description>
			<content:encoded><![CDATA[<p>This is a problem with your script and/or your web server. The error means that you are attempting to pass back to a file does not have the necessary permissions on the server to receive Post information from another script. If you have administrative or root access to your server, be sure that this file has been set up to be treated as a script and that the appropriate user accounts have read and execute permissions on the script. If you are in a shared hosting situation, please contact your server administrator or the support department for your host.</p>
<p>HTTP errors are not generated specifically by 2Checkout. They are a part of the HTTP protocol and are common amongst all web servers. It is therefore beyond the realm of 2Checkouts support to provide you with specific instructions for making these changes as every server is set up differently and 2CO does not provide server administration services as part of our support plan.</p>
<p>To test and see if your file set up is correct:</p>
<ol>
<li>Create a new text file using a text editor such as Windows Notepad.</li>
<li> Paste the following code into this new file:<br />
<strong> &lt;form method=&#8221;POST&#8221; action=&#8221;[full URL to Your Script Here]&#8220;&gt;<br />
&lt;input type=&#8221;hidden&#8221; name=&#8221;test&#8221; value=&#8221;1&#8243;&gt;<br />
&lt;input type=&#8221;submit&#8221; value=&#8221;Test Script&#8221;&gt; &lt;/form&gt;</strong></li>
<li> Replace &#8220;[full URL to Your Script Here]&#8221; with the URL of the script you are attempting to pass back to. Remember that this should be the full URL of your script, including the http:// portion.</li>
<li> Save the file as an HTML file, such as &#8220;test.html&#8221; or &#8220;test.htm&#8221; to your desktop and close your text editor.</li>
<li> Open the file in your web browser and click the &#8220;Test Script&#8221; button that is displayed.</li>
<li> If you receive the message again, the problem is in your script and/or on your server. Note that the exact wording of the error message may vary slightly depending on your browser and your servers configuration. If you see something about &#8220;method not allowed&#8221; or &#8220;error 405&#8243; then the information above pertains to your situation.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-405-on-passback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

