You're giving the right answer to the wrong question. ;-) Chad's question had nothing to do with limits on GET parameters or the maximum length of a URL. The parameters were making it to the server just fine.
The question was about any possible limits on the *response*. This wouldn't be affected by the use of GET vs. POST. The answer turned out to be that the server code wasn't using a proper JSON encoder, so it was leaving newlines inside strings in the JSON response, which of course broke it. -Mike > From: MorningZ > > "GET vs. POST would have nothing to do with this" > > Sure it could..... > > http://classicasp.aspfaq.com/forms/what-is-the-limit-on-querystring/get/url- parameters.html > > Granted i do not know if newer browser versions have raised > or removed that cap, but it's still something to consider > > > To original poster: it would take a minute to switch from > $.getJSON and it's default GET behavior to the more generic > $.ajax() method and setting method to POST >
