There must be some. When it comes to PHP specifically, php.ini has a limit of most post. By default, the maximum data transmission is 8M. If it is converted into characters, it may not be calculated. After all, there are methods for calculating characters in Chinese and English. The difference is that even if the transmission limit is continuously expanded, the number of characters transmitted will still be exceeded, so please transmit tens of thousands of data in segments. Even if the maximum limit is not exceeded, the more data is transmitted, the slower the corresponding speed will be.
There is no clear limit on the size of HTTP response.
Generally, the server returns data to the client. If the server knows the size of the returned content, it can be specified through the Content-Length header.
If the server itself does not know the specific size of data returned to the client (such as streaming data), it can use Chunked Transfer-Encoding to identify it.
However, it is not a good idea for the server to return large segments of JSON, as it will cause the client to take too long to parse, and the user experience is not good. The best way is to paginate/segment the data, asynchronously, and request while parsing.
A request returns a large amount of json data, and the front-end parsing time is also very long. If asynchronous processing is not performed, the thread may be stuck. It is best to request in segments
Yes, but you must consider the capabilities of both ends, especially the performance of the server, and the stability of the transmission. Generally speaking this is not recommended.
I object to the previous ones who confused requests and responses. There is no size limit for downloads. It seems that when you download a file through http request, it will not say that the file cannot be downloaded if it is larger than the size. Returning json is actually responding to a byte file. So, unless the php execution times out during your return process, there is no return size problem.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
There must be some. When it comes to PHP specifically, php.ini has a limit of most post. By default, the maximum data transmission is 8M. If it is converted into characters, it may not be calculated. After all, there are methods for calculating characters in Chinese and English. The difference is that even if the transmission limit is continuously expanded, the number of characters transmitted will still be exceeded, so please transmit tens of thousands of data in segments. Even if the maximum limit is not exceeded, the more data is transmitted, the slower the corresponding speed will be.
There is no clear limit on the size of HTTP response.
Generally, the server returns data to the client. If the server knows the size of the returned content, it can be specified through the
Content-Lengthheader.If the server itself does not know the specific size of data returned to the client (such as streaming data), it can use Chunked Transfer-Encoding to identify it.
However, it is not a good idea for the server to return large segments of JSON, as it will cause the client to take too long to parse, and the user experience is not good. The best way is to paginate/segment the data, asynchronously, and request while parsing.
A request returns a large amount of json data, and the front-end parsing time is also very long. If asynchronous processing is not performed, the thread may be stuck. It is best to request in segments
Yes, but you must consider the capabilities of both ends, especially the performance of the server, and the stability of the transmission. Generally speaking this is not recommended.
Not recommended, you can use paging and ajax to load
I object to the previous ones who confused requests and responses.
There is no size limit for downloads. It seems that when you download a file through http request, it will not say that the file cannot be downloaded if it is larger than the size.
Returning json is actually responding to a byte file.
So, unless the php execution times out during your return process, there is no return size problem.