authorize.net hex coded variables

This WebDNA talk-list message is from

2002

It keeps the original formatting. numero = 45802
interpreted = N
texte = If you are one of the ones wrestling with Authorize.net's changed incomingvariables as of last Monday (11/18), I have a definitive answer. Last nightI was back and forth with one of their techs, and am proud to say I figuredit out for them after several tests and a dive into the WebCat docs on[UnURL]. Turns out, problem is that they are passing lowercased hexcodes,not uppercased ones. WebCat automatically converts uppercased hexcodes,which is why we never had a problem before. Now, with whatever they didlast week, hexcodes with letters in them are not getting converted. That'swhy spaces are fine (%20), but periods are not (%2e). The tech guy(Patrick) told me:>I think you're right. We have logged this in our system and our engineers>will soon be looking at it. As there are quite a few open issues>currently, you should probably include the modifier in your script. This>is probably affecting all case sensitive scripting languages so we>appreciate you pointing this out to us. This will most likely be fixed>around the first of the year as we cannot make any changes to our code>until the end of the Holiday shopping season.I figured that was a fair trade; after all, it took me a lot of persistenceto finally break through some dispatcher who didn't understand the problemand get to someone who knew what I was talking about. And now at least theyagree there's a problem worth fixing.So my question is this. Using WebCat 3, how can I best convert thesehexcodes? [UnURL] only works on uppercase in version 3, and I am not readyto see if 4.5 will work on my setup (4.0 did not), as I plan to upgrade theserver before too long and will do it then. I don't want to uppercaseeverything. I can write my own variables to a db and retrieve them fromthere (and have done that for the mission critical variables), butconverting the incoming variables is cleaner and it would take care of theAuthnet originated variables.Terry WilsonAttitude 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/ Associated Messages, from the most recent to the oldest:

Re: authorize.net hex coded variables OOPS (Terry Wilson 2002)
Re: authorize.net hex coded variables (Terry Wilson 2002)
Re: authorize.net hex coded variables (Gary Krockover 2002)
Re: authorize.net hex coded variables (Terry Wilson 2002)
Re: authorize.net hex coded variables (Clint Davis 2002)
Re: authorize.net hex coded variables (Gary Krockover 2002)
Re: authorize.net hex coded variables (Ejaz Syed 2002)
Re: authorize.net hex coded variables (John Peacock 2002)
Re: authorize.net hex coded variables (Clint Davis 2002)
Re: authorize.net hex coded variables (Terry Wilson 2002)
Re: authorize.net hex coded variables (Gary Krockover 2002)
authorize.net hex coded variables (Terry Wilson 2002)

If you are one of the ones wrestling with Authorize.net's changed incomingvariables as of last Monday (11/18), I have a definitive answer. Last nightI was back and forth with one of their techs, and am proud to say I figuredit out for them after several tests and a dive into the WebCat docs on[unurl]. Turns out, problem is that they are passing lowercased hexcodes,not uppercased ones. WebCat automatically converts uppercased hexcodes,which is why we never had a problem before. Now, with whatever they didlast week, hexcodes with letters in them are not getting converted. That'swhy spaces are fine (%20), but periods are not (%2e). The tech guy(Patrick) told me:>I think you're right. We have logged this in our system and our engineers>will soon be looking at it. As there are quite a few open issues>currently, you should probably include the modifier in your script. This>is probably affecting all case sensitive scripting languages so we>appreciate you pointing this out to us. This will most likely be fixed>around the first of the year as we cannot make any changes to our code>until the end of the Holiday shopping season.I figured that was a fair trade; after all, it took me a lot of persistenceto finally break through some dispatcher who didn't understand the problemand get to someone who knew what I was talking about. And now at least theyagree there's a problem worth fixing.So my question is this. Using WebCat 3, how can I best convert thesehexcodes? [unurl] only works on uppercase in version 3, and I am not readyto see if 4.5 will work on my setup (4.0 did not), as I plan to upgrade theserver before too long and will do it then. I don't want to uppercaseeverything. I can write my own variables to a db and retrieve them fromthere (and have done that for the mission critical variables), butconverting the incoming variables is cleaner and it would take care of theAuthnet originated variables.Terry WilsonAttitude 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/ Terry Wilson

DOWNLOAD WEBDNA NOW!

authorize.net hex coded variables

2002

Top Articles:

Related Readings: