It should be possible to get it to use the POST method. In SOLO, there is a currently a bug that you cannot use the magic "lzpostbody" parameter to force it to post a raw string as the content, but you should be able to get it to use POST method for a normal dataset.

Can you send me a very small example of your dataset and how you are setting it's query type?

I will try to reproduce it in the current trunk release.


                                                                                                       































                                    




























m,.llppooppppppppooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo                                                                                                                                                                                                                               kk k kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk                                                                                                                                                                                      

On 9/6/06, Mike at TOL23Design <[EMAIL PROTECTED] > wrote:
Hallo people !
 
I am in somewhat of a bind..
I have developed a fairly large form with a couple of hundred fields and I submit it fine when I use the app in Firefox.
IE however, will not tolerate character strings over 2038, so does not even send a request, as revealed my headers proxy debugger thingy.
This also shows me that despite trying to set the 'setQueryType' to POST, the request when it goes from FF is still a GET.
This is a solo-deployed app. and I think I read that this is a known bug, that the setQueryType does not activate under SOLO...
Any thoughts on the best approach to fixing this ? (and saving the relationship with my client, lol :)..
Naturally, I am lax to break up the form into several seperate ones, although I could do that transparently, and have the submit button submit them all at once.
This would be rather cumbersome on the php, which would need to be rewritten somewhat.
Any thoughts/hacks on how I might achieve my goal most efficiently ?
 
Thanks for everything !
 
Mike,


_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user





--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user

Reply via email to