Forums / General Questions / 302 Redirect error with worldpay mod

302 Redirect error with worldpay mod

Locked

Results 1 to 2 of 2

This thread is locked. New replies are disabled.

23 May 2007, 12:06 PM

crazycucumber

Zen Follower

Join Date:: Jan 2006
Posts:: 403
Plugin Contributions:: 0

302 Redirect error with worldpay mod

Hi , I have a thread in the Payment Modules Contributions , but I wonder if anyone can shed some light on this response message :-

HTTP/1.1 302 Found
Date: Wed, 23 May 2007 10:51:12 GMT
Server: Apache/1.3.37 (Unix) mod_fastcgi/2.4.2 PHP/5.1.2 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 

FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Location: /
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="/">here</A>.<P>
<HR>
<ADDRESS>Apache/1.3.37 Server at www.bodycast-studio.co.uk Port 80</ADDRESS>
</BODY></HTML>

This is the reponse that worldpay are getting when trying to go back to the checkout success page , I just wondered if anyone knew how this 302 error page comes from and why it is being invoked. ? thanks

23 May 2007, 12:27 PM

crazycucumber

Zen Follower

Join Date:: Jan 2006
Posts:: 403
Plugin Contributions:: 0

Re: 302 Redirect error with worldpay mod

Hi again , just had a response from the host admins - but it still doesn't work .

this is what they said-

It was due to mod_security restriction on server. You can check the exact logs here :

[Wed May 23 12:35:41 2007] [error] [client 155.136.68.34] mod_security: Access denied with redirect to [/]. Pattern match "!(^$|^application/x-www-form-urlencoded$|^multipart/form-data)" at HEADER("Content-Type") [severity "EMERGENCY"] [hostname "www.bodycast-studio.co.uk"] [uri "/index.php?main_page=wpcallback&msgType=authResult&zenid=4b9c3caf8d6eaf227cc327f964e94cf3&installation=123554"]

I have excluded your domain from mod_sec restriction. Now you should not get any such error again.
Could you please give a try one more time.

Regards,
Senior Admin
Support Team.