I think there is some issue with the internal jetty http producer classes. I changed the endpoint's name at jetty's end and gave an uri through processor using CamelHttpUri, but it still produced same behavior.
Logs : [2013-05-28 11:24:18,366] org.apache.camel.processor.SendProcessor DEBUG - >>>> *Endpoint[https://googleserver/maps/api/place/photo?bridgeEndpoint=false&throwExceptionOnFailure=false]* Exchange[Message: [Body is null]] [2013-05-28 11:24:18,369] org.apache.camel.component.jetty.JettyHttpProducer DEBUG - *Sending HTTP request to: https//maps.googleapis.com:443/maps/api/place/photo?maxwidth=80&photoreference=CnRoAAAAmGXSPqV7_E_P0o8JeCr6xXH4DLJZsm3-od2lJWVjtLGoa5pl_yDoufwBuGl1pw-3OhBxHvXLOWWJACQxuy1nJdm2uPwSVsEqPNZpml85tNfntMvQtuRb63HZybXAk5hr62Y-wvJOA2jCXVxcAOciuRIQ02-DFJ3aWT5O3HAir_DGBxoUuab9uUKGbSELn4j9-SduNVWVUwM&sensor=true&key=encrypted&client=blahblah* [2013-05-28 11:24:18,394] org.apache.camel.component.jetty.JettyContentExchange DEBUG - TaskComplete with state 7 for url: https//maps.googleapis.com:443/maps/api/place/photo?maxwidth=80&photoreference=CnRoAAAAmGXSPqV7_E_P0o8JeCr6xXH4DLJZsm3-od2lJWVjtLGoa5pl_yDoufwBuGl1pw-3OhBxHvXLOWWJACQxuy1nJdm2uPwSVsEqPNZpml85tNfntMvQtuRb63HZybXAk5hr62Y-wvJOA2jCXVxcAOciuRIQ02-DFJ3aWT5O3HAir_DGBxoUuab9uUKGbSELn4j9-SduNVWVUwM&sensor=true&key=encrypted&client=blahblaha [2013-05-28 11:24:18,395] org.apache.camel.component.jetty.DefaultJettyHttpBinding DEBUG - HTTP responseCode: 404 Why does it replaces https:// with https//, or is there something else ? -- View this message in context: http://camel.465427.n5.nabble.com/Using-jetty-component-for-http-producer-Weird-behavior-tp5733303p5733344.html Sent from the Camel - Users mailing list archive at Nabble.com.
