Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
curl_easy_escape is limited to 8MB of urlencoded data #6190
Since change ed35d65 the function curl_easy_escape fails if the url encoded data grows bigger than 8MB (CURL_MAX_INPUT_LENGTH).
Is it a wanted change? I didn't see any release notes about it.
It should be at least be documented. And I think it should be configurable too.
If it wasn't mentioned, it was an oversight.
The idea with the limit is to reject strings that are mistakes/abuses, not to prevent any valid use cases. Are you saying that you actually URL encode strings longer than 8 megabytes with curl?
And yes, the limit should be documented clearly!
Thanks for your response.
Yes, It happens that we have more than 8MB of data to urlencode. We didn't have this problem earlier until we upgrade the curl version.
I'm considering to switch to multipart/form-data at least for problematic cases, but I have to deal with different curl versions in production environment (Windows and RedHat), and the API for mime changed in 7.56.0, that's why I didn't do it earlier.