Re: authorize.net hex coded variables
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 46052
interpreted = N
texte = Since wrapping all variables in the [UnURL IGNORECASE=T][variable][/UnURL] fixes what A/N is returning and won't munge information that is already in the proper format, I've taken no chances and just wrapped everything in it.Run this example:[UnURL IGNORECASE=T]382%2d9229[/UnURL]
[UnURL IGNORECASE=T]auth%5fonly[/UnURL]
[UnURL IGNORECASE=T]auth_only[/UnURL]
[UnURL IGNORECASE=T]382-9229[/UnURL]
[UnURL IGNORECASE=T]Normal text here[/UnURL]You'll see the results are good for every test case.Might be overkill, but I figured it would save some headaches of wondering where something wasn't getting converted when it should be.GK| Ejaz, | | Greg is correct with the unurl codes for incoming variables... | | [UnURL IGNORECASE=T][variable][/UnURL] | | As for your .inc file, here are the variables that come back with munged | codes (all periods, dashes, commas, a few others -- any hex code with a | letter in it.). The values below were returned to me on a test, so you can | decide if they'd cause problems. Most of the variables (alphanumeric-only | ones) are fine (What I did is put a [formvariables] on the return page to | view everything as it comes back.): | | x_phone=382%2d9229 <---problem with dashes | x_type=auth%5fonly <---problem with underscore | x_amount=39%2e00 <---problem with period | x_tax=0%2e0000 <---problem with period (for the rest of them) | x_duty=0%2e0000 | x_freight=0%2e0000 | ipAddress=209%2e066%2e015%2e072 | email=terry@terryfic%2ecom | x_response_reason_text=This transaction has been approved%2e | | Right off the bat, I see your [showif] using x_type is going to fail for | you. The underscore is hexed. So wrap that one in the [UnURL] for sure. | Probably just making that one change will get you by until A/N fixes their | little problem. Once you get that one fixed so the [setheader] will work, | open the cart to see if you can live with whatever hex codes get written to | the cart, or just [unurl] the problematic ones. | | So replace your second line below with: | [showif [UnURL][Uppercase][x_type][/Uppercase][/UnURL]=auth_capture] | | -------- | [!] Purchse Results [/!] | [showif [x_type]=auth_capture] | [FileInfo file=[ordersFolder][x_invoice_num]][showif [IsFile]=T] | | [setheader | file=[ordersFolder][x_invoice_num]]payMethod=OB_CC&status=[__status]&authNum | ber=[x_auth_code]&responseText=[x_avs_code]:[x_response_reason_text]&referen | ceNumber=[x_trans_id]&batchnum=&refnum=&sequencenum=&header5=[x_MD5_Hash] | [/setheader] | [/showif] | | [/FileInfo] | [redirect [lookup | db=WebMerchantPrefs.db&lookinfield=preference&value=AuthorizeNet_Thanks&retu | rnfield=value]?cart=[x_invoice_num]] | -------- | The redirect to AuthorizeNetThanks.tpl shouldn't be a problem,as the only | variable passed is the cart, which is numbers only. | | Thanks, Greg, for the kind words. As for A/N support, I am an EXTREMELY | patient person, but even I almost lost it a couple of times there with A/N | support. Whew, what an ordeal. | | Hope this helps you get back to making some $$, | Terry | | >Is anyone out there working with Authorize Net, where are the best minds, | >KEN? | > | >After spending few hours with A/N engineers today and yesterday | >(1877-4773-3938), I'm clueless about which portion of AuthorizeNet.inc file | >need to be debugged for incoming variables. BTW, the A/N engineers have not | >heard of WebDNA! | | >Notice that the landing page AutorizeNet.tpl redirects to | >AuthorizeNetThanks.tpl. | > | >Terry Wilson, what is your approach to this problem in WebDNA 4.5 | > | >John, where may we add [UnURL][Uppercase]returnfield[/Uppercase][/UnURL] | >in the template. | | Attitude is the only difference between an ordeal and an adventure. | _____________________________________________________________________ | (If I don't write back right away, I'm just buried in email. | Feel free to nudge me.) | ===================================================================== | | ------------------------------------------------------------- | This message is sent to you because you are subscribed to | the mailing list
. | To unsubscribe, E-mail to: | To switch to the DIGEST mode, E-mail to | Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Since wrapping all variables in the [UnURL IGNORECASE=T][variable][/UnURL] fixes what A/N is returning and won't munge information that is already in the proper format, I've taken no chances and just wrapped everything in it.Run this example:[UnURL IGNORECASE=T]382%2d9229[/UnURL]
[UnURL IGNORECASE=T]auth%5fonly[/UnURL]
[UnURL IGNORECASE=T]auth_only[/UnURL]
[UnURL IGNORECASE=T]382-9229[/UnURL]
[UnURL IGNORECASE=T]Normal text here[/UnURL]You'll see the results are good for every test case.Might be overkill, but I figured it would save some headaches of wondering where something wasn't getting converted when it should be.GK| Ejaz, | | Greg is correct with the unurl codes for incoming variables... | | [UnURL IGNORECASE=T][variable][/UnURL] | | As for your .inc file, here are the variables that come back with munged | codes (all periods, dashes, commas, a few others -- any hex code with a | letter in it.). The values below were returned to me on a test, so you can | decide if they'd cause problems. Most of the variables (alphanumeric-only | ones) are fine (What I did is put a [formvariables] on the return page to | view everything as it comes back.): | | x_phone=382%2d9229 <---problem with dashes | x_type=auth%5fonly <---problem with underscore | x_amount=39%2e00 <---problem with period | x_tax=0%2e0000 <---problem with period (for the rest of them) | x_duty=0%2e0000 | x_freight=0%2e0000 | ipAddress=209%2e066%2e015%2e072 | email=terry@terryfic%2ecom | x_response_reason_text=This transaction has been approved%2e | | Right off the bat, I see your [showif] using x_type is going to fail for | you. The underscore is hexed. So wrap that one in the [unurl] for sure. | Probably just making that one change will get you by until A/N fixes their | little problem. Once you get that one fixed so the [setheader] will work, | open the cart to see if you can live with whatever hex codes get written to | the cart, or just [unurl] the problematic ones. | | So replace your second line below with: | [showif [unurl][uppercase][x_type][/Uppercase][/UnURL]=auth_capture] | | -------- | [!] Purchse Results [/!] | [showif [x_type]=auth_capture] | [FileInfo file=[ordersFolder][x_invoice_num]][showif [IsFile]=T] | | [setheader | file=[ordersFolder][x_invoice_num]]payMethod=OB_CC&status=[__status]&authNum | ber=[x_auth_code]&responseText=[x_avs_code]:[x_response_reason_text]&referen | ceNumber=[x_trans_id]&batchnum=&refnum=&sequencenum=&header5=[x_MD5_Hash] | [/setheader] | [/showif] | | [/FileInfo] | [redirect [lookup | db=WebMerchantPrefs.db&lookinfield=preference&value=AuthorizeNet_Thanks&retu | rnfield=value]?cart=[x_invoice_num]] | -------- | The redirect to AuthorizeNetThanks.tpl shouldn't be a problem,as the only | variable passed is the cart, which is numbers only. | | Thanks, Greg, for the kind words. As for A/N support, I am an EXTREMELY | patient person, but even I almost lost it a couple of times there with A/N | support. Whew, what an ordeal. | | Hope this helps you get back to making some $$, | Terry | | >Is anyone out there working with Authorize Net, where are the best minds, | >KEN? | > | >After spending few hours with A/N engineers today and yesterday | >(1877-4773-3938), I'm clueless about which portion of AuthorizeNet.inc file | >need to be debugged for incoming variables. BTW, the A/N engineers have not | >heard of WebDNA! | | >Notice that the landing page AutorizeNet.tpl redirects to | >AuthorizeNetThanks.tpl. | > | >Terry Wilson, what is your approach to this problem in WebDNA 4.5 | > | >John, where may we add [unurl][uppercase]returnfield[/Uppercase][/UnURL] | >in the template. | | Attitude is the only difference between an ordeal and an adventure. | _____________________________________________________________________ | (If I don't write back right away, I'm just buried in email. | Feel free to nudge me.) | ===================================================================== | | ------------------------------------------------------------- | This message is sent to you because you are subscribed to | the mailing list . | To unsubscribe, E-mail to: | To switch to the DIGEST mode, E-mail to | Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Gary Krockover
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
pictures / referrer etc. (1998)
UPDATE PROBLEM (1997)
[random] only for 1-100??? (1997)
[WebDNA] SkipJack Authorize interface help (2009)
WebCat2.0 [format thousands .0f] no go (1997)
Error: unknown exception (2000)
Searching multiple fields from one form field (1997)
The & Problem (1998)
Same Database needed on two machines (2002)
template security preferences????? (1998)
WebCat b13 CGI -shownext- (1997)
Multiple prices (1997)
suffix mapping for NT? (1997)
Server Load (2000)
PIXO Support (1997)
Special characters in field names (1998)
Sorting (1998)
[shell] error? (2005)
Exclude by date - multiple (1997)
Upgrading old WebCat Database Files (1997)