Re: authorize.net hex coded variables

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 46078
interpreted = N
texte = >Does anyone know if this is affecting other server-side scripting languages >like ColdFusion, ASP, PHP, etc.? Surely, WebDNA isn't the only language >affected.Any case-sensitive language. WebDNA automatically decodes hexcodes -- but only if they're in all caps -- so you aren't aware of it. Authnet's text stream is now coming with lowercase characters, causing some of the hexcodes to pass through as clear text (ascii chart http://www.danbbs.dk/~erikoest/asciicc.htm to see what codes involve characters). If those other languages only parse uppercase hexcodes, then yes, they will have problems. It's our saving grace that this could cause problems with more mainstream languages; otherwise I don't think they would have given a damn about our WebDNA problem.Here's what I got from the tech at Authnet:At 8:18 PM -0800 11/27/02, support@authorize.net wrote: >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.Hope this helps, TerryAttitude 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)
>Does anyone know if this is affecting other server-side scripting languages >like ColdFusion, ASP, PHP, etc.? Surely, WebDNA isn't the only language >affected.Any case-sensitive language. WebDNA automatically decodes hexcodes -- but only if they're in all caps -- so you aren't aware of it. Authnet's text stream is now coming with lowercase characters, causing some of the hexcodes to pass through as clear text (ascii chart http://www.danbbs.dk/~erikoest/asciicc.htm to see what codes involve characters). If those other languages only parse uppercase hexcodes, then yes, they will have problems. It's our saving grace that this could cause problems with more mainstream languages; otherwise I don't think they would have given a damn about our WebDNA problem.Here's what I got from the tech at Authnet:At 8:18 PM -0800 11/27/02, support@authorize.net wrote: >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.Hope this helps, TerryAttitude 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!

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:

[WriteFile] problems (1997) [WebDNA] Problem with Trigers. (2013) Accented chars and emailer (1998) search w/international chars (1999) Search in 2 or more catalogs (1997) Trouble with formula.db (1997) Sorry I didn't pay attention-but ??? (1997) Just Testing (1997) Preventing Merchant Settling ? (1997) unable to launch acgi in WebCat (1997) Can you do this??? and other stuff (1997) New Lawsuit Alleges Unitedhealth/Pacificare Deceived (2006) Maybe off topic but how to charge (1997) pull downs (1997) PLEASE REMOVE MY EMAIL ADDRESS (1997) It just Does't add up!!! (1997) WebCatalog2 Feature Feedback (1996) Date or time comparisons have bugs ... (1998) Log-in Scheme (2003) Multiple security dbs (1997)