On Tue, 28 Dec 2010 08:50:01 +0200 Andrej Shadura wrote:
Hello,
On Mon, 27 Dec 2010 21:29:15 +0100 (CET)
Daniel Stenberg 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
>
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.
Hello,
On Sat, 11 Dec 2010 19:10:45 +0100 (CET)
Daniel Stenberg dan...@haxx.se wrote:
I'm sorry but I'm completely missing the point here.
What are you suggesting (lib)curl should do and when?
HTML4 standard says:
Space characters are replaced by
`+', and then reserved characters are
Hello,
On Mon, 27 Dec 2010 18:45:36 +0200
Andrew O. Shadoura bugzi...@tut.by wrote:
I think the beast way would be making a curl option that enables
Sorry, the BEST way, not the BEAST :)
--
WBR, Andrew
signature.asc
Description: PGP signature
Hello,
On Mon, 27 Dec 2010 19:18:09 +0100 (CET)
Daniel Stenberg dan...@haxx.se wrote:
So, you're saying that you have a server that doesn't understand %20
as space but insists on spaces to appear as '+'?
Besides nitpicking, I'm trying to understand what problem you're
trying to solve.
No,
Hello,
On Mon, 27 Dec 2010 19:31:36 +0100 (CET)
Daniel Stenberg dan...@haxx.se wrote:
The reverse?
curl encodes the data, surely your server end needs to DECODE the
data then?
Curl has both encode and decode functions. I use decode.
Also, some libraries depend on curl to perform this
Hello,
On Sun, 21 Feb 2010 23:26:18 +0100 (CET)
Daniel Stenberg dan...@haxx.se wrote:
See --data-urlencode
curl supports urlencoding just fine.
Daniel, have you read my message? Have you tried the code above?
First, I'm speaking of cURL as library, not a separate program.
But okay, let's
Hello,
On Sat, 11 Dec 2010 17:12:56 +0200
Andrew O. Shadoura bugzi...@tut.by wrote:
That doesn't follow RFC1738.
Oops, that's exactly RFC1738 but not application/x-www-form-urlencoded.
cURL does RFC1738 but doesn't application/x-www-form-urlencoded, and
that's what I'm really speaking about.
Hi,
I'm sorry but I'm completely missing the point here.
What are you suggesting (lib)curl should do and when?
--
/ daniel.haxx.se
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
See --data-urlencode
curl supports urlencoding just fine.
--
/ daniel.haxx.se
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: curl
Version: 7.19.5-1
Severity: normal
Hello.
cURL doesn't support application/x-www-form-urlencoded encoding, and this is
stated explicitly nowhere in the documentation, thus causing much confustion
As per http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1,
11 matches
Mail list logo
