Re: 256 character limit in URL? Kinda urgent...
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 59903
interpreted = N
texte = Phil Herring wrote: > This is the Bank of America eStores system, which works like the old > authorize.net gateway, I believe. > > The checkout form is posted to the B of A server, where the card and address > info are captured. Then the user is invisibly redirected back to our server > with the authorization data in this massive URL. Here's an example: > > https://www.domain.com/process.tpl?m=SBA&IOC_merchant_order_id=&IOC_merchant > _shopper_id=&IOC_shopper_id=TQ7L6R71DK4F8G5VEF3K84GRFG9R4556&IOC_response_co > de=7&Ecom_transaction_complete=TRUE&IOC_pcard_response=N&Ecom_Payment_Card_V > erification_RC=&IOC_missing_fields=&IOC_invalid_fields=(Ecom_Payment_Card_Nu > mber,,%2AUnknown+Card+Type%280%29%2A+is+not+an+accepted+Credit+Card%2E++Plea > se+use+a+different+credit+card+for+this+purchase%2E),(Ecom_Payment_Card_ExpD > ate_Month,1,The+expiration+month%2Fyear+is+invalid%2E)&IOC_Invalid_Request=& > IOC_reject_description=There+are+invalid+fields%2E&fno=400&cart=109962233432 > 155&requiredconfirm=T > > You can see the cart number near the end of the URL -- it is passed through > B of A and back to us. Using the cart number we match the B of A auth data > to the shopping cart and append the whole mess to our db's. > > What I can't figure is why this worked great in OS9/W*4/webdna4 for three > years and now with OSX/W*5/webdna6 (I tried it in 4.5, too) it breaks. > > Looks like I'll have to go back and re-install the G3 tomorrow. Maybe I'll > test it on a Commodore 64... Though most proxies and webservers allow greater than 256 characters these days, its never a good idea (from what I've read) to go above that. I would have guessed what Stuart said last,... that somewhere in your code, you are running up against one of the orderfile field restrictions... but you say this exact code was working for you before so thats probably not the problem. I suggest that you try to isolate the issue with testing, but ultimately, the problem is because of your overly large URL's being passed. Donovan -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE Eucalyptus Design <-Web Development (specializing in eCommerce), -> <- Graphic Design, Custom Tags and Labels -> ADDRESS:> Donovan Brooke DBA Eucalyptus Design N2862 Summerville Park Rd. Lodi, WI 53555 PH:> 1.608.592.3567 Web:> http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- 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:
Phil Herring wrote: > This is the Bank of America eStores system, which works like the old > authorize.net gateway, I believe. > > The checkout form is posted to the B of A server, where the card and address > info are captured. Then the user is invisibly redirected back to our server > with the authorization data in this massive URL. Here's an example: > > https://www.domain.com/process.tpl?m=SBA&IOC_merchant_order_id=&IOC_merchant > _shopper_id=&IOC_shopper_id=TQ7L6R71DK4F8G5VEF3K84GRFG9R4556&IOC_response_co > de=7&Ecom_transaction_complete=TRUE&IOC_pcard_response=N&Ecom_Payment_Card_V > erification_RC=&IOC_missing_fields=&IOC_invalid_fields=(Ecom_Payment_Card_Nu > mber,,%2AUnknown+Card+Type%280%29%2A+is+not+an+accepted+Credit+Card%2E++Plea > se+use+a+different+credit+card+for+this+purchase%2E),(Ecom_Payment_Card_ExpD > ate_Month,1,The+expiration+month%2Fyear+is+invalid%2E)&IOC_Invalid_Request=& > IOC_reject_description=There+are+invalid+fields%2E&fno=400&cart=109962233432 > 155&requiredconfirm=T > > You can see the cart number near the end of the URL -- it is passed through > B of A and back to us. Using the cart number we match the B of A auth data > to the shopping cart and append the whole mess to our db's. > > What I can't figure is why this worked great in OS9/W*4/webdna4 for three > years and now with OSX/W*5/webdna6 (I tried it in 4.5, too) it breaks. > > Looks like I'll have to go back and re-install the G3 tomorrow. Maybe I'll > test it on a Commodore 64... Though most proxies and webservers allow greater than 256 characters these days, its never a good idea (from what I've read) to go above that. I would have guessed what Stuart said last,... that somewhere in your code, you are running up against one of the orderfile field restrictions... but you say this exact code was working for you before so thats probably not the problem. I suggest that you try to isolate the issue with testing, but ultimately, the problem is because of your overly large URL's being passed. Donovan -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE Eucalyptus Design <-Web Development (specializing in eCommerce), -> <- Graphic Design, Custom Tags and Labels -> ADDRESS:> Donovan Brooke DBA Eucalyptus Design N2862 Summerville Park Rd. Lodi, WI 53555 PH:> 1.608.592.3567 Web:> http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- 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/
Donovan Brooke
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:
F3 crashing server (1997)
garbage on page (2000)
showif field is number (1997)
Order not created error (never mind) (1997)
RE: Going to anchors within a template page (1997)
Associative lookup style? (1997)
NT beta ReadMe missing (b12-b15) (1997)
[WebDNA] More wish-list requests implemented (2016)
WCS Newbie question (1997)
A question on sub-categories (1997)
https validation (2001)
Re[2]: When do we get to request new features? (1999)
RE: [WebDNA] XML Help (2009)
Re[2]: Re[2]: New syntax feedback for 4.0 (2000)
is sku a REQUIRED field on NT (1997)
RedHat Linux glibc version 2.1.2 or higher required (2000)
PCS Frames (1997)
How is it done? (1998)
Date Sorting (1997)
Aaron kant add (or whatever it was) (2000)