What you really should note is the limit of the weakest, which is the lowest limit among all the components involved in the process.
For the URL, even if other components accept a limit higher than 2048 bytes, Internet Explorer cannot send more, so you should work with this limit unless you are ensuring that no user will use IE, which is very unlikely. Still, I’d still have that limit to make sure. For both GET and POST, this is the limit that the URL should have, but with POST it is possible to send data beyond the URL, GET, only send by URL.
The HTTP protocol does not impose any limit on sending data via POST. But the HTTP server may be set to some limit.
In theory none browser imposes some limit.
PHP usually has a relatively low limit that works most of the time. Other languages may have some limitations.
Even if you decide to change this limit of PHP or HTTP server, think about it, it can cause problems. It is not easy to manipulate large data shipments. Apart from the fact that sending may have problems in the middle, so both the server and the client need to know how to handle it. It may be better to split the shipment if the data to be sent is too large, and obviously needs to manage forwards.
So the element limit is not what matters. If you already have several elements and summed they are very large, it is better to send separately if possible.
That’s not W3C is w3schools
– Jorge B.
It is that they are very different, and known for very different reasons. W3C is reliable. w3schools not so much.
– Jorge B.
If it is in PHP, the php.ini directive defines this. N case, it is defined by the directive
max_post_size
the limit of data sent in the post (in Megabites)– Wallace Maxters
In this case, as there is no php tag in your post, I preferred to generalize the answer :)
– Wallace Maxters
The question idea is even generic.... how data is passed by the header of a request
Cliente-Servidor
, there should probably be a maximum size of POST information for the transfer, in each source I seek I find a different information.– MarceloBoni
Like I said: It’s good to have a limit. In php, for example, POST is converted into an array. A giant array generates a memory overflow. You can overhead in some cases, rsrsrsrs
– Wallace Maxters
@Marceloboni no good or forgot this? If I can improve something just say.
– Maniero
@mustache I had completely forgotten about her =]
– MarceloBoni