Re: Unexpected job status encountered

2018-12-27 Thread Karl Wright
Thanks for looking harder into this! The credential encoding in httpcomponents/httpclient has been problem free as far as I have seen, so if you determine that that's the issue I am sure it will be news to a lot of people. But by using the wire logging you should be able to see the headers,

Re: Unexpected job status encountered

2018-12-27 Thread Erlend GarĂ¥sen
It wasn't necessary to deal with tools like tcpdump etc. Adding the following to the logging.xml did the trick: So now I know what's going on. Bad credentials: DEBUG 2018-12-27T11:18:41,593 (Thread-1508) - http-outgoing-2 << "HTTP/1.1 401 Unauthorized[\r][\n]" Strange, because connection