Not sure it'll make a difference, but have you considered using POST rather than get?
On Thu, Aug 6, 2015 at 12:23 PM, Richard Gaskin <ambassa...@fourthworld.com> wrote: > I don't think it's the URL length. URL length may sometimes be an issue, > but most often only for the server; since this works in a browser I think > it may be reasonably safe to rule that out. > > Cookies won't appear in the data, but they can be seen with whatever tools > your browser provides for examining cookies. However, since this is an > intermittent problem with a high success rate, I don't think this is > related to required cookies not being provided. > > Have you tried other combinations of words of similar total length in both > the browser and LC? Maybe it's a specific set of words, or the way they're > URL encoded, or something else along those lines. > > Can you share the full URL of an example that fails? > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > > Roger Eller wrote: > >> Richard, if I view source of the result in a browser, it is just text, >> exactly as the database spits it out, no formatting as it is not meant for >> browser/human consumption. I haven't used or needed to use cookies >> before. This application works for 99% of the requests. Based on the >> size >> of the words searched for, usually 316 is the most it can get in a single >> URL. I just did one with 392, and it worked in the browser, but not >> LiveCode. >> >> ~Roger >> >> On Thu, Aug 6, 2015 at 1:09 PM, Richard Gaskin <ambassador at >> fourthworld.com> >> wrote: >> >> Roger Eller wrote: >>> >>> > The URL is really long, so maybe I am hitting some upper limit within >>> > LiveCode. The same URL pasted into a browser (chrome) receives a >>> > result, but get URL within LiveCode does not. The parameter is just a >>> > long list my server script looks up in a database. The list length >>> > varies. >>> >>> Could there be session info in that URL? Or perhaps the server is >>> expecting a cookie that the browser provides but is not provided by your >>> script's handling of the headers? >>> >>> -- >>> Richard Gaskin >>> >> > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
