Re: [WebDNA] [BULK] Web Merchant Authorize net issues
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106523
interpreted = N
texte = --001636c594ff0c89d204a0cf98ac Content-Type: text/plain; charset=ISO-8859-1 I got experience with Authorize.net and a working script. It's also depends on your account settings with Authorize.net. If you still need help, give me a call... 419-913-4594 -Scott On Wed, Apr 6, 2011 at 1:38 PM, Arturo Vargas
wrote: > I have created a store with store builder and I am trying to setup > authorizenet with it and I am not able to get the transactions over to > authorizenet. > > As a Payment Authorization Method I am using: CC-Auth Capture > > I have tried these two things: > > Payment Processor: AuthorizeNet - Direct Connect Method > I get this as a response Text when viewing the orders: > > This transaction cannot be accepted. > Hash: EF1C72BD6F66C2C5D2156D6607E1EB4B > > And Status: Error > > ---------------------------------------------------------------------------- > ----------------------------- > > Payment Processor: AuthorizeNet > I get no response Text when viewing the orders > > And Status: Waiting_734598.0739 > > Any help would be greatly appreciated. > > > > Art > > > > -----Original Message----- > From: Chris Wik [mailto:chris@anu.net] > Sent: Wednesday, April 06, 2011 12:41 AM > To: talk@webdna.us > Subject: Re: [WebDNA] TCP HTTP/1.1 questions > > On 06.04.2011, at 05:28, Aaron Michael Kaczmarek wrote: > > > I reviewed the protocol and it seems that chunked transfer-encoding is > probably the source of this problem. I don't imagine webDNA supports > persistent connections, so a "Connection: Close" header must be included. > I'll try this out tomorrow and let ya know what I get. > > > It sounds like both ends are using KeepAlive (which is assumed to be > supported by HTTP/1.1), and neither end is closing the connection until the > keepalive timeout is reached. > > Connection: close in the HTTP header informs the other end that you will > not > be sending any further requests and wish to close the HTTP connection as > soon as the request is complete. > > -- > Chris Wik > Anu Internet Services Ltd > www.cwik.ch | www.anu.net > > --------------------------------------------------------- > This message is sent to you because you are subscribed to the mailing list > . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --001636c594ff0c89d204a0cf98ac Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I got experience =A0with Authorize.net and a working script. It's also = depends on your account settings with Authorize.net.
If = you still need help, give me a call... 419-913-4594
-Scott
On Wed, Apr 6, 2011 at 1:38 PM, Ar= turo Vargas
<art= v@cssimpact.com> wrote:
I have created a store with store builder and I am trying to setup
authorizenet with it and I am not able to get the transactions over to
authorizenet.
As a Payment Authorization Method I am using: CC-Auth Capture
I have tried these two things:
Payment Processor: AuthorizeNet - =A0Direct Connect Method
I get this as a response Text when viewing the orders:
This transaction cannot be accepted.
Hash: EF1C72BD6F66C2C5D2156D6607E1EB4B
And Status: Error
---------------------------------------------------------------------------= -
-----------------------------
Payment Processor: AuthorizeNet
I get no response Text when viewing the orders
And Status: Waiting_734598.0739
Any help would be greatly appreciated.
Art
-----Original Message-----
From: Chris Wik [mailto:chris@anu.net]=
Sent: Wednesday, April 06, 2011 12:41 AM
To: talk@webdna.us
Subject: Re: [WebDNA] TCP HTTP/1.1 questions
On 06.04.2011, at 05:28, Aaron Michael Kaczmarek wrote:
> I reviewed the protocol and it seems that chunked transfer-encoding is=
probably the source of this problem. =A0I don't imagine webDNA supports=
persistent connections, so a "Connection: Close" header must be i= ncluded.
I'll try this out tomorrow and let ya know what I get.
It sounds like both ends are using KeepAlive (which is assumed to be
supported by HTTP/1.1), and neither end is closing the connection until the=
keepalive timeout is reached.
Connection: close in the HTTP header informs the other end that you will no= t
be sending any further requests and wish to close the HTTP connection as soon as the request is complete.
--
Chris Wik
Anu Internet Services Ltd
www.cwik.ch | www.anu.net
---------------------------------------------------------
This message is sent to you because you are subscribed to the mailing list<= br> <talk@webdna.us>.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
--001636c594ff0c89d204a0cf98ac--
Associated Messages, from the most recent to the oldest: