My mistake. I had the HTTPService defined twice. On Dec 4, 2007 11:37 AM, Richard Rodseth <[EMAIL PROTECTED]> wrote:
> Hmm. I'm certain I am not calling send(params) with empty data, and I > assume that when an HTTPService is constructed it doesn't send anything on > it's own. In one of my apps I construct the HTTPService on the fly when a > (business) service method is invoked, but in this one, I construct it in the > main MXML file, with data binding involved for the host prefix. I think I'll > switch to on-the-fly in all cases. > > > On Dec 4, 2007 11:06 AM, Mike Nimer <[EMAIL PROTECTED]> wrote: > > > I've seen the same behavior. If I remember right I tracked it down to > > being an issue If you don't post any form data with the request flash > > ignores the method="post" that you set and changes it back to GET for you. > > > > > > > > Hth, > > > > --nimer > > > > > > > > > > > > *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On > > Behalf Of *Richard Rodseth > > *Sent:* Tuesday, December 04, 2007 12:45 PM > > *To:* flexcoders@yahoogroups.com > > *Subject:* Re: [flexcoders] More 2032 fun > > > > > > > > It appears that the problem was that the service was doing a GET rather > > than a POST. Which is puzzling, because I set method="POST" in an MXML file. > > I'll try to figure out where the switch occurs. > > > > On Dec 3, 2007 5:42 PM, Tracy Spratt <[EMAIL PROTECTED]> wrote: > > > > I have used HTTPService POST with IE6 and some quite large (1.2MB) data > > with out problem. Hmm, that big one was with Flex 1.5, haven't moved > > that much with 2.x yet. > > > > Tracy > > > > > > ------------------------------ > > > > *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On > > Behalf Of *Richard Rodseth > > *Sent:* Monday, December 03, 2007 7:32 PM > > *To:* flexcoders@yahoogroups.com > > *Subject:* [flexcoders] More 2032 fun > > > > > > > > Does anyone know of any size issues with HttpService POST data in IE6 > > and IE7? We're seeing #2032 stream errors when some dynamically created data > > reaches a threshold. I'm not sure what the threshhold is in bytes, but it's > > not very large, and the other browsers don't have the same problem. Thanks. > > > > > > > > > > > >
