I guess the surprise was his alert *appeared* to be dependent on the
response size, and "of course" he did not get an error message.
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
"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 po
Query
(English)";
Subject: [jQuery] Re: getJSON response limit
Well, the response actually returns, but the jQuery code do
I used json_encode in php to escape the new-lines and all works great
now!
Well, the response actually returns, but the jQuery code doesn't
execute. I've isolated the problem--I have a field in the database
that stores general instructions that can be entered by a user. There
is a carriage return for new-lines in the text that is captured. When
one of these entries is
There is no set limit on the size of a JSON response, any more than there is
on an HTML or XML response. You can have very large JSON responses with no
problem.
GET vs. POST would have nothing to do with this. Those are only different in
the way the request is sent to the server; the response for
7 matches
Mail list logo
