Kryptronic Software Support Forum
You are viewing this forum as a guest. Login to an existing account, or create a new account, to reply to topics and to create new topics.
#1 07-20-2013 12:32:24
- lazarus42
- Member
- Registered: 11-22-2005
- Posts: 29
v8.05 worldpay integration issues
I have just migrated our main production site from CCPv5.1 with ATS SEO to CCPv8.05. All very scary.
All is working fine except for worldpay integration callbacks which from messages on the site seems to be an area a few others have had issues with.
We have
http://www.oursite.co.uk/utilities/ecomrelaymeta.php
set in the Payment Response URL field on worldpay's site.
We have
Payment Response enabled?
ticked.
Orders are creating a callback failure error email, viz:
Our systems have detected that your callback has failed.
This callback failure means we were unable to pass information
to your server about the following transaction:
Transaction ID: 2673262525
Cart ID: AWB201307201
Installation ID: 103828
Error reported: Callback to http://www.angelwholesale.co.uk/utiliti … ymeta.php: NOT OK, recevied HTTP status: 301
Server Reference: mm2imsps1p:callbackFailureEmail-84035:MerchReq-167-11
Any suggestions? We currently have worldpay off and so so paypal which is not ideal.
Phill
Offline
#2 07-21-2013 14:50:04
- lazarus42
- Member
- Registered: 11-22-2005
- Posts: 29
Re: v8.05 worldpay integration issues
The problem remains. My suspicion is that as we have changed our server at the same time as going from CCP5.1 to CCP8.0.5 worldpay may track the TCP/IP address associated with our domainname and so not be callingback to the right place. I will speak to them in the morning to check.
Offline
#3 07-22-2013 02:45:43
- lazarus42
- Member
- Registered: 11-22-2005
- Posts: 29
Re: v8.05 worldpay integration issues
So worldpay assure me that they do not track the TCP/IP address. They say the 301 HTTP status is the problem. Trying to look at htaccess file and permissions now.
Offline
#4 07-22-2013 03:20:48
- lazarus42
- Member
- Registered: 11-22-2005
- Posts: 29
Re: v8.05 worldpay integration issues
Hmm. htaccessfile is below. It definitely is redirecting. Verified with htaccess checker http://htaccess.madewithlove.be/
Options +FollowSymLinks
RewriteEngine On
# Old SEO Rule Rewrites
RewriteRule ^cat--(.*)--(.*)\.html index.php?app=ecom&ns=catshow&ref=$2 [L,PT]
RewriteRule ^item--(.*)--(.*)\.html index.php?app=ecom&ns=prodshow&ref=$2 [L,PT]
RewriteRule ^page--(.*)--(.*)\.html index.php?app=cms&ns=display&ref=$2 [L,PT]
RewriteRule ^store index.php?app=ecom&ns=splash [L,PT]
RewriteRule ^splash index.php?app=cms&ns=display&ref=splash [L,PT]
# Version 8 Rewrite Rules
RewriteRule ^index.php - [L,PT]
RewriteRule ^$ index.php?COREseourl=/ [L,PT]
RewriteRule ^/$ index.php?COREseourl=/ [L,PT]
RewriteRule ^sitemap\.xml utilities/sitemap.xml [L,PT]
RewriteRule ^rss\.xml utilities/rss.xml [L,PT]
RewriteCond %{REQUEST_URI} ^/
RewriteCond %{REQUEST_URI} !\.(xml|css|js|gif|jpg|jpeg|png|pdf)$ [NC]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php?COREseourl=/$1 [L,PT]
Offline
#5 07-22-2013 07:52:48
Re: v8.05 worldpay integration issues
It appears you corrected this issue as:
http://angelwholesale.co.uk/utilities/ecomrelay.php
Is now responding without a redirect. I assume you just updated to 8.0.5, which changed the relay method from https only to http (to support sites without https). This may have resolved your issue.
Nick Hendler
Offline
#6 07-22-2013 07:57:35
Re: v8.05 worldpay integration issues
Jeff is going to follow up in the ticket system on this with you. You've opened a forum topic, submitted a support ticket and emailed us directly on the same issue since Friday. You will only receive a response from Kryptronic on this from here on out via the ticket system.
Nick Hendler
Offline
#7 07-22-2013 08:09:46
- lazarus42
- Member
- Registered: 11-22-2005
- Posts: 29
Re: v8.05 worldpay integration issues
I have just checked using http://web-sniffer.net/ and the redirect is still there, viz:
HTTP Request Header
Connect to 212.48.64.96 on port 80 ... ok
TRACE /utilities/ecomrelaymeta.php HTTP/1.1[CRLF]
Host: wwwangelwholesale.co.uk[CRLF]
Connection: close[CRLF]
User-Agent: Googlebot/2.1 (+http://www.googlebot.com/bot.html)[CRLF]
Accept-Encoding: gzip[CRLF]
Accept-Charset: ISO-8859-1,UTF-8;q=0.7,*;q=0.7[CRLF]
Cache-Control: no-cache[CRLF]
Accept-Language: de,en;q=0.7,en-us;q=0.3[CRLF]
Referer: http://web-sniffer.net/[CRLF]
[CRLF]
with a reply of:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://angelwholesale.co.uk/utilities/ecomrelaymeta.php">here</a>.</p>
<hr>
<address>Apache Server at wwwangelwholesale.co.uk Port 80</address>
</body></html>
Offline
#8 07-23-2013 11:06:16
- lazarus42
- Member
- Registered: 11-22-2005
- Posts: 29
Re: v8.05 worldpay integration issues
Nick resolved this today. Entirely my fault.
Details below if anyone else is in this sorry position...
I had a rewrite rule in my htaccess file which rewrote a URL of the format wwwoursite.co.uk to oursite.co.uk One of the standard recommended ones for CCP8 I believe.
In the callback on worldpay I had wwwoursite.co.uk/utilities/ecommrelay.php The 'www.' is the problem.
apache rightly rewrote this as oursite.co.uk/utilities/ecommrelay.php sending back a 301 moved permanently code which worldpay then interprets as it cannot get through to the relay code.
Fixed and all worked.
Thank you, Nick :-)
Offline