Bugs item #1956383, was opened at 2008-05-02 20:54
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1956383&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: client module
Group: wrong behaviour
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: carlos vicente dorca (cvicented)
Assigned to: Daniel Stenberg (bagder)
Summary: curl binary doesn't complain with RFC 2396

Initial Comment:
curl version: 7.18.1
OS: Red Hat Linux 4 ES Update 4.

Curl binary doesn't complain RFC 2396 for whitespaces in URI.
If you do a request adding whitespaces in the url, curl doesn't convert these whitespaces in US-ASCII coded character 20 hexadecimal (%20).
 
This behaviour doesn't complain RFC 2396:

RFC 2396:
......
2.4.3. Excluded US-ASCII Characters

   Although they are disallowed within the URI syntax, we include here a
   description of those US-ASCII characters that have been excluded and
   the reasons for their exclusion.

   The control characters in the US-ASCII coded character set are not
   used within a URI, both because they are non-printable and because
   they are likely to be misinterpreted by some control mechanisms.

   control = <US-ASCII coded characters 00-1F and 7F hexadecimal>

   The space character is excluded because significant spaces may
   disappear and insignificant spaces may be introduced when URI are
   transcribed or typeset or subjected to the treatment of word-
   processing programs. Whitespace is also used to delimit URI in many
   contexts.

   space = <US-ASCII coded character 20 hexadecimal>
.....

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2008-05-02 22:12

Message:
Logged In: YES
user_id=1110
Originator: NO

This is by design. This is not a bug.

curl accepts URLs and by including whitespaces you pass in something that
isn't a URL

curl is liberal in what it accepts and tries hard to make something out of
almost anything you pass to it.

If you think this design issue isn't good, then I suggest you take the
discussion to the curl-users mailing list and start arguing for your case
and why curl should be modified to support what you ask for.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1956383&group_id=976
Received on 2008-05-02