Re: [BULK] RE: [WebDNA] [BULK] Web Merchant Authorize net issues

This WebDNA talk-list message is from

2011

It keeps the original formatting. numero = 106499
interpreted = N
texte = Art,Yes, you have to allow the WebLink Connection method to allow or accept =HTTPS connections from the server.=20Tony Millertmiller@thehawkeye.comOn Apr 6, 2011, at 5:47 PM, Arturo Vargas wrote:> Tony,=20>=20> Thanks for your response.>=20> Are to referring to the WebLink that needs to be enabled?>=20> Art>=20> -----Original Message-----> From: Tony Miller [mailto:tmiller@thehawkeye.com]=20> Sent: Wednesday, April 06, 2011 1:24 PM> To: talk@webdna.us> Subject: Re: [WebDNA] [BULK] Web Merchant Authorize net issues> Importance: Low>=20> Art,>=20> I have a couple accounts set up with Auth.net. You have to go into the =setup> for the account and do two things:>=20> First is enable the ability for the account to accept connections from =your> web server. I think it's 'webconnect' or something like that.=20>=20> Second is to generate a set of security codes that have to be entered =in the> WebDNA setups for the store. 'Generate Passcodes' or 'Generate =Security> keys', I can't remember, it's been a long time since I set one up.=20>=20> You also have to make sure the paths to the Sandbox and other prefs =are all> set correctly.=20>=20> I use the CC-Auth Capture setting also and it works flawlessly - once =you> get all the pieces in place.=20>=20> I'll try to log in to my Auth.net account and get a better description =of> the settings you have to configure to get it to work. I also had one =account> where the bank did not set up the account so it COULD accept =connections> from an ecommerce site, so they had to scrap that account and set up =one> that could.=20>=20> Tony Miller> tmiller@thehawkeye.com>=20> On Apr 6, 2011, at 12:38 PM, Arturo Vargas wrote:>=20>> I have created a store with store builder and I am trying to setup=20>> authorizenet with it and I am not able to get the transactions over =to=20>> authorizenet.>>=20>> As a Payment Authorization Method I am using: CC-Auth Capture>>=20>> I have tried these two things:>>=20>> Payment Processor: AuthorizeNet - Direct Connect Method I get this =as=20>> a response Text when viewing the orders:>>=20>> This transaction cannot be accepted.>> Hash: EF1C72BD6F66C2C5D2156D6607E1EB4B>>=20>> And Status: Error>> =---------------------------------------------------------------------->> ------>> ----------------------------->>=20>> Payment Processor: AuthorizeNet>> I get no response Text when viewing the orders>>=20>> And Status: Waiting_734598.0739>>=20>> Any help would be greatly appreciated.>>=20>>=20>>=20>> Art>>=20>>=20>>=20>> -----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>>=20>> On 06.04.2011, at 05:28, Aaron Michael Kaczmarek wrote:>>=20>>> I reviewed the protocol and it seems that chunked transfer-encoding=20=>>> is>> probably the source of this problem. I don't imagine webDNA supports=20=>> persistent connections, so a "Connection: Close" header must be =included.>> I'll try this out tomorrow and let ya know what I get.>>=20>>=20>> It sounds like both ends are using KeepAlive (which is assumed to be=20=>> supported by HTTP/1.1), and neither end is closing the connection=20>> until the keepalive timeout is reached.>>=20>> Connection: close in the HTTP header informs the other end that you=20=>> will not be sending any further requests and wish to close the HTTP=20=>> connection as soon as the request is complete.>>=20>> -->> Chris Wik>> Anu Internet Services Ltd>> www.cwik.ch | www.anu.net>>=20>> --------------------------------------------------------->> This message is sent to you because you are subscribed to the mailing=20=>> list .>> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us>>=20>> --------------------------------------------------------->> This message is sent to you because you are subscribed to the mailing=20=>> list .>> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us>=20> ---------------------------------------------------------> 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>=20> ---------------------------------------------------------> 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 Associated Messages, from the most recent to the oldest:

RE: [BULK] RE: [WebDNA] [BULK] Web Merchant Authorize net issues ("Arturo Vargas" 2011)
Re: [BULK] RE: [WebDNA] [BULK] Web Merchant Authorize net issues (Tony Miller 2011)
[BULK] RE: [WebDNA] [BULK] Web Merchant Authorize net issues ("Arturo Vargas" 2011)

Art,Yes, you have to allow the WebLink Connection method to allow or accept =HTTPS connections from the server.=20Tony Millertmiller@thehawkeye.comOn Apr 6, 2011, at 5:47 PM, Arturo Vargas wrote:> Tony,=20>=20> Thanks for your response.>=20> Are to referring to the WebLink that needs to be enabled?>=20> Art>=20> -----Original Message-----> From: Tony Miller [mailto:tmiller@thehawkeye.com]=20> Sent: Wednesday, April 06, 2011 1:24 PM> To: talk@webdna.us> Subject: Re: [WebDNA] [BULK] Web Merchant Authorize net issues> Importance: Low>=20> Art,>=20> I have a couple accounts set up with Auth.net. You have to go into the =setup> for the account and do two things:>=20> First is enable the ability for the account to accept connections from =your> web server. I think it's 'webconnect' or something like that.=20>=20> Second is to generate a set of security codes that have to be entered =in the> WebDNA setups for the store. 'Generate Passcodes' or 'Generate =Security> keys', I can't remember, it's been a long time since I set one up.=20>=20> You also have to make sure the paths to the Sandbox and other prefs =are all> set correctly.=20>=20> I use the CC-Auth Capture setting also and it works flawlessly - once =you> get all the pieces in place.=20>=20> I'll try to log in to my Auth.net account and get a better description =of> the settings you have to configure to get it to work. I also had one =account> where the bank did not set up the account so it COULD accept =connections> from an ecommerce site, so they had to scrap that account and set up =one> that could.=20>=20> Tony Miller> tmiller@thehawkeye.com>=20> On Apr 6, 2011, at 12:38 PM, Arturo Vargas wrote:>=20>> I have created a store with store builder and I am trying to setup=20>> authorizenet with it and I am not able to get the transactions over =to=20>> authorizenet.>>=20>> As a Payment Authorization Method I am using: CC-Auth Capture>>=20>> I have tried these two things:>>=20>> Payment Processor: AuthorizeNet - Direct Connect Method I get this =as=20>> a response Text when viewing the orders:>>=20>> This transaction cannot be accepted.>> Hash: EF1C72BD6F66C2C5D2156D6607E1EB4B>>=20>> And Status: Error>> =---------------------------------------------------------------------->> ------>> ----------------------------->>=20>> Payment Processor: AuthorizeNet>> I get no response Text when viewing the orders>>=20>> And Status: Waiting_734598.0739>>=20>> Any help would be greatly appreciated.>>=20>>=20>>=20>> Art>>=20>>=20>>=20>> -----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>>=20>> On 06.04.2011, at 05:28, Aaron Michael Kaczmarek wrote:>>=20>>> I reviewed the protocol and it seems that chunked transfer-encoding=20=>>> is>> probably the source of this problem. I don't imagine webDNA supports=20=>> persistent connections, so a "Connection: Close" header must be =included.>> I'll try this out tomorrow and let ya know what I get.>>=20>>=20>> It sounds like both ends are using KeepAlive (which is assumed to be=20=>> supported by HTTP/1.1), and neither end is closing the connection=20>> until the keepalive timeout is reached.>>=20>> Connection: close in the HTTP header informs the other end that you=20=>> will not be sending any further requests and wish to close the HTTP=20=>> connection as soon as the request is complete.>>=20>> -->> Chris Wik>> Anu Internet Services Ltd>> www.cwik.ch | www.anu.net>>=20>> --------------------------------------------------------->> This message is sent to you because you are subscribed to the mailing=20=>> list .>> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us>>=20>> --------------------------------------------------------->> This message is sent to you because you are subscribed to the mailing=20=>> list .>> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us>=20> ---------------------------------------------------------> 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>=20> ---------------------------------------------------------> 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 Tony Miller

DOWNLOAD WEBDNA NOW!

Re: [BULK] RE: [WebDNA] [BULK] Web Merchant Authorize net issues

2011

Top Articles:

Related Readings: