Hi Pedro,
Somehow this discussion slipped by my radar a bit here and went unanswered, sorry :).
Yes our encoding APIs always encode a space character as %20, which is correct according to RFC 3986. We do this instead of the older '+'. You can see more details about this on Wikipedia and stackoverflow threads.
If you absolutely have to have the '+' encoding behavior you will have to use something different.
Steve
Somehow this discussion slipped by my radar a bit here and went unanswered, sorry :).
Yes our encoding APIs always encode a space character as %20, which is correct according to RFC 3986. We do this instead of the older '+'. You can see more details about this on Wikipedia and stackoverflow threads.
If you absolutely have to have the '+' encoding behavior you will have to use something different.
Steve