Hi Robert,

I think you're quite right, the limitation is probably on Witango. But Chuck, 
was your length testing with @URL or just hand-crafted in MSIE?

Here's a link to some interesting bits of information about URL limits.

http://www.boutell.com/newfaq/misc/urllength.html

Obviously browsers have their limits, which we've all run into at some point or 
another, but server-to-server should be more wide open.

All the best.

Scott,



On Friday, February 8, 2008 11:55am, Robert Garcia <[EMAIL PROTECTED]> said:

> I have some webservices I use, with actual banks, like FDR, and
> cardservices, that require HORRENDOUSLY long get arguments. The only
> time there is a limit, is if it is imposed by the client, or the
> server. So if the server has no limit, and I would imagine this is the
> case with a webservice that requires xml in the get argument, then I
> would suspect either @url is putting the brakes on it, or your xml
> needs to be prepared to fit on a single line, and URLENCODED.
> 
> I have a conference call in 7 mins, with a bank with a service like
> this, and they don't even allow you to substitute as POST args, must
> be get.
> 
> The other way to check, is write something in VB and test it. I use
> RealBasic, and have not found a limit on GET.
> 
> One more note, I know that witango has a limit, due to memory
> allocation, on the size of an environment variable passed to a
> external app. My guess, is they have some limit on this also.
> 
> --
> 
> Robert Garcia
> President - BigHead Technology
> VP Application Development - eventpix.com
> 13653 West Park Dr
> Magalia, Ca 95954
> ph: 530.645.4040 x222 fax: 530.645.4040
> [EMAIL PROTECTED] - [EMAIL PROTECTED]
> http://bighead.net/ - http://eventpix.com/
> 
> On Feb 8, 2008, at 7:32 AM, Scott Cadillac wrote:
> 
>> Hi Chuck,
>>
>> Unfortunately there is an unspecified limit to how long you can make
>> a URL. GET requests were never meant to support long strings of
>> data, thus the POST request. People try, but eventually somewhere in
>> the URL's travels a proxy, router or gateway somewhere will start
>> truncating the URL.
>>
>> Are you sure you're interpretting the webservice's specs correctly?
>>
>> Do you have any more information you can post?
>>
>> Let us know, when you have time.
>>
>> Scott,
>>
>>
>>
>> On Friday, February 8, 2008 11:23am, Chuck Lockwood <[EMAIL PROTECTED]
>> > said:
>>
>>> We are using a webservice that requires that the XML be passed in
>>> as a get,
>>> not a post argument (so it seems).
>>>
>>>
>>>
>>> The below works until the <@ARG testXML> gets over 2000 characters
>>> then it
>>> starts getting truncated.  Am I nuts or does witango do this?
>>>
>>>
>>>
>>> <@ASSIGN request$method_response VALUE="<@URL LOCATION='<@ARG
>>> vURL>&xml=<@ARG TestXML>'>">
>>>
>>>
>>>
>>> Suggestions?
>>>
>>>
>>>
>>> Chuck Lockwood
>>>
>>> President
>>>
>>>
>>>
>>>
>>> ............................................
>>>
>>> 309 Main Avenue
>>> Hawley, Pa 18428
>>> (P) 570.226.7340
>>> (F) 570.226.7341
>>>
>>> www.lockdata.com <http://www.lockdata.com/>
>>>
>>>
>>>
>>>
>>> ________________________________________________________________________
>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>>
>> ________________________________________________________________________
>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>>
> ________________________________________________________________________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
> 
> 

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to