I’ve been using CURLSMBS for years now without any issues, happily uploading and downloading files with spaces in their names to both FTP and SFTP sites. Now, after updating CURLMBS from 21.0 to 21.4, any URL containing spaces returns an error of 3.
If I revert my MBSCURL plug-in to 21.0, the program works again.
I see that just about every new release of MBS involves an update to the latest CURL library, and I assume this was something that happened in the CURL project and not at MBS - can anyone confirm? Seems like a change that could break a lot of code.
I presume that’s %20 instead of a space then? Couldn’t curl automatically convert to the stricter format? Then it wouldn’t break older code.
A blog post about the changes and what specifically has changed would be useful too.
That’s one of those that I call a “Thoreau-Change”. Thoreau measured everything in how much life-time it would cost. In this case 1 developer can make the change in under 10 min, or possibly thousands of developers spend a lot longer each with updating their code and testing their apps, wasting a lot of life-time in the process.
When I originally started using CURL and saw that it accepted spaces, I was like “Oh, that’s so thoughtful of them to make it that much more human-friendly”.
Absolutely correct re Thoreau. I’m just glad I found the issue before deploying broken apps.
Yeah, I updated my question I know the usual characters to avoid but wondering if the CURL team changed anything else recently that they used to allow, like spaces.
EncodeURLComponent escapes forward slashes, so it doesn’t seem to be much use for FTP file URLs unless there are options I’m not aware of (can’t find any documentation). I’m just escaping spaces myself for the moment.