Hi
I do think it may be better to make this configurable and keep the old
behavior as default (so Camel stays the same).
And then allow to turn on to use %20 as spaces for the HTTP components
so this can be used for HTTP servers that has problems.
For non HTTP components then its the "problem"
Hi
I am currently working on an outstanding "issue" we have with the way
endpoint URIs have been encoded and decoded by Camel. It goes back to
Camel 1.x and 2.x.
However here for Camel 3 we have improved the parser and optimized it
in various ways, that it allows the opportunity to get one last
