Re: authorize.net hex coded variables

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 45804
interpreted = N
texte = I'm not sure that I understand what you fix is Terry?Also, are your pages passing the referring url? Nobody has gotten back to me on this, so I don't know if the problem is the hexcoded crap or the not passing of the referring URL.We don't have 4.5 on the box that has the clients using A/N so the TCPConnect is not an option for us at this point. Actually, I think we have 2 options: find a quick and reliable fix for the A/N mess (and fast) or move to something else.We're looking at Verisign's Payflow Plus. Who all has horror stories about it?GK> If you are one of the ones wrestling with Authorize.net's changed incoming > variables as of last Monday (11/18), I have a definitive answer. Last night > I was back and forth with one of their techs, and am proud to say I figured > it 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 did > last week, hexcodes with letters in them are not getting converted. That's > why 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 persistence > to finally break through some dispatcher who didn't understand the problem > and get to someone who knew what I was talking about. And now at least they > agree there's a problem worth fixing. > > So my question is this. Using WebCat 3, how can I best convert these > hexcodes? [UnURL] only works on uppercase in version 3, and I am not ready > to see if 4.5 will work on my setup (4.0 did not), as I plan to upgrade the > server before too long and will do it then. I don't want to uppercase > everything. I can write my own variables to a db and retrieve them from > there (and have done that for the mission critical variables), but > converting the incoming variables is cleaner and it would take care of the > Authnet originated variables. > > Terry Wilson > > 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/ Associated Messages, from the most recent to the oldest:

    
  1. Re: authorize.net hex coded variables OOPS (Terry Wilson 2002)
  2. Re: authorize.net hex coded variables (Terry Wilson 2002)
  3. Re: authorize.net hex coded variables (Gary Krockover 2002)
  4. Re: authorize.net hex coded variables (Terry Wilson 2002)
  5. Re: authorize.net hex coded variables (Clint Davis 2002)
  6. Re: authorize.net hex coded variables (Gary Krockover 2002)
  7. Re: authorize.net hex coded variables (Ejaz Syed 2002)
  8. Re: authorize.net hex coded variables (John Peacock 2002)
  9. Re: authorize.net hex coded variables (Clint Davis 2002)
  10. Re: authorize.net hex coded variables (Terry Wilson 2002)
  11. Re: authorize.net hex coded variables (Gary Krockover 2002)
  12. authorize.net hex coded variables (Terry Wilson 2002)
I'm not sure that I understand what you fix is Terry?Also, are your pages passing the referring url? Nobody has gotten back to me on this, so I don't know if the problem is the hexcoded crap or the not passing of the referring URL.We don't have 4.5 on the box that has the clients using A/N so the TCPConnect is not an option for us at this point. Actually, I think we have 2 options: find a quick and reliable fix for the A/N mess (and fast) or move to something else.We're looking at Verisign's Payflow Plus. Who all has horror stories about it?GK> If you are one of the ones wrestling with Authorize.net's changed incoming > variables as of last Monday (11/18), I have a definitive answer. Last night > I was back and forth with one of their techs, and am proud to say I figured > it 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 did > last week, hexcodes with letters in them are not getting converted. That's > why 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 persistence > to finally break through some dispatcher who didn't understand the problem > and get to someone who knew what I was talking about. And now at least they > agree there's a problem worth fixing. > > So my question is this. Using WebCat 3, how can I best convert these > hexcodes? [unurl] only works on uppercase in version 3, and I am not ready > to see if 4.5 will work on my setup (4.0 did not), as I plan to upgrade the > server before too long and will do it then. I don't want to uppercase > everything. I can write my own variables to a db and retrieve them from > there (and have done that for the mission critical variables), but > converting the incoming variables is cleaner and it would take care of the > Authnet originated variables. > > Terry Wilson > > 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/ 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:

trouble updating records in database (1998) WC Database Format (1997) Show shoppingcart after remove last item (1997) problem serving foreign languages text (1997) P1: How to make webcatalog more stable. - LONG (1999) Search returns all, not 20 (1997) WebCat2b13MacPlugIn - syntax to convert date (1997) Listfiles on network with NT (2000) Triggers (2003) Emailer Set Up (1997) Just Testing (1997) automatic reload of frameset (1997) Location of Browser Info.txt file (1997) Duplicate emails with bcc (2000) Logging purchases (1997) WebCat2b15MacPlugin - showing [math] (1997) stray LF character in the email (2003) WebCommerce: Folder organization ? (1997) Pirated WebCat? NOT... (2003) customers getting same cart (2004)