JSONP response becomes unconditional

I am trying to use a JSONP response in a cross platform. I use HTML and jQuery Mobile. Sometimes, when there are no more records, the response is automatically cut off after a fixed absence of attributes, it does not read the complete response, as in JSON format. I could not get the full answer. However, the same answer works fine for JSON and can be easily used on Android.

In a cross-platform application, in a browser, when I checked it, it was damned, who has an idea about this? It would be really noticeable if someone could help with this.

UPDATE

On Apache Tomcat, it works fine, but for the JBOSS application server I ran into a problem. Can the problem maxHttpHeaderSize. Pls tell me what maxHttpHeaderSize actually affects this.?

+4
source share
2 answers

JSON can be processed through a POST request, JSONP is always GET, and most web servers limit the length of a GET request to 8192 bytes (8 KB)

+3
source

I don’t think that the accepted answer correctly describes your problem, since your problem is related to the answer and size limits, as a rule, to the length of the request URL ... There are many web pages on the Internet that are larger than 8 KB and they immediately they are sent back.

, : tomcat nginex, , -, nginex 64 . , jquery , ( jquery, ). , Tomcat w/o nginex , , , , Tomcat .

( ), , , , ( 0-99, 100-199 .., 100 ), .

+2

Source: https://habr.com/ru/post/1534808/


All Articles