On Thu, Sep 13, 2012 at 10:31 AM, Christian Müller
wrote:
> Hello Claus!
>
> Feel free to grap the ticket. At present I don't work on it and I would be
> happy to have this solved soon.
>
I have attached a patch to the ticket
https://issues.apache.org/jira/browse/CAMEL-4857
This allows component
I have logged a ticket about the user info issue when using @ in the
user name or password
https://issues.apache.org/jira/browse/CAMEL-5603
That said though, using %40 instead of @ works fine.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twi
>
> On Wed, Sep 12, 2012 at 8:51 AM, Marco Crivellaro
> wrote:
>> Thanks for letting me know.
>> The ticket doesn't have any target milestone, is there a short term plan to
>> work on this issue?
>> Othewise I suppose the only way out for me would be to roll b
-containing-40-or-26-tp5719118p5719257.html
Sent from the Camel - Users mailing list archive at Nabble.com.
milestone, is there a short term plan
> to
> > work on this issue?
> > Othewise I suppose the only way out for me would be to roll back to last
> > 2.8.x...
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/
ose the only way out for me would be to roll back to last
> 2.8.x...
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Issues-with-URI-containing-40-or-26-tp5719118p5719165.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus I
h-URI-containing-40-or-26-tp5719118p5719165.html
Sent from the Camel - Users mailing list archive at Nabble.com.
der version which supports %40 and %26 in URI until this is URISupport is
> fixed. Would 2.9.x be ok?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Issues-with-URI-containing-40-or-26-tp5719118p5719132.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
in which version have this behaviour been introduced? I'd prefer to use an
older version which supports %40 and %26 in URI until this is URISupport is
fixed. Would 2.9.x be ok?
--
View this message in context:
http://camel.465427.n5.nabble.com/Issues-with-URI-containing-40-
sword=t%26st
--
View this message in context:
http://camel.465427.n5.nabble.com/Issues-with-URI-containing-40-or-26-tp5719118p5719128.html
Sent from the Camel - Users mailing list archive at Nabble.com.
t; View this message in context:
> http://camel.465427.n5.nabble.com/Issues-with-URI-containing-40-or-26-tp5719118p5719121.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fuseso
Claus Ibsen-2 wrote
>
> Give 2.10.1 a try
>
2.10.1 have issues as well
valid uri: ftp://us%40r@host?password=t%26st
is normalized to invalid uri: ftp://us@r@host?password=t&st
--
View this message in context:
http://camel.465427.n5.nabble.com/Issues-with-URI-contai
for this issue to be fixed earlier? It seems to me quite a big for a
> great framework like Camel is.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Issues-with-URI-containing-40-or-26-tp5719118.html
> Sent from the Camel - Users mailing list
ke there is no workaround for this.
The issue has been scheduled to be fixed for version 2.11... is there any
chance for this issue to be fixed earlier? It seems to me quite a big for a
great framework like Camel is.
--
View this message in context:
http://camel.465427.n5.nabble.com/Issues-with
14 matches
Mail list logo
