On Tue, 28 Dec 2010 08:50:01 +0200 Andrej Shadura <bugzi...@tut.by> wrote:
Hello,
On Mon, 27 Dec 2010 21:29:15 +0100 (CET)
Daniel Stenberg <dan...@haxx.se> wrote:
> > '+' MUST be supported. I need to decode it using curl. I'm unable
> > to do this currently.
> Ah, now I think understand what you're saying. You say you want
> curl_easy_unescape() to convert '+' into space. Right?
Yes, possibly CR/LF translation should be done, too, I haven't checked
if curl does it yet. Also, I'd like curl_easy_escape to convert space
to '+' because sometimes that's important too (e.g. protocols like
OAuth rely on both sides to perform conversion the same way).
> I'm afraid we can't do that easily without breaking older apps. We
> should clarify the docs to make this described better.
That's why I suggest you to make a CURLOPT_RFC1738 option (enabled by
default) disabling which will switch it to W3C's behaviour.
Re-reading my old bug reports — oh man, I wish I knew how to be polite
to other people back then. Being young and not a very fluent English
speaker didn’t help, too :)
Daniel, I’m really sorry for the way I reported this issue back in the
day. (I hope) I’m much more pleasant a person to talk to these days.
In any case, I’m wondering, what’s the status of this these days?
I don’t need this feature anymore, but I’m not sure what to do about
this bug report.
--
Cheers,
Andrej
