Ah, I see, thank you. Adding a "WWW-Authenticate" to the test makes it
pass. It sends a request with no auth, is challenged, and sends a request
with auth.
Is there any way to enable preemptive auth for credentialy in the request
URI, without having to parse them out first in order to set up a
C
On Sun, 2015-07-12 at 12:43 -0700, Derek Lewis wrote:
> Ok, that seems reasonable. However, I'm still confused about the behaviour.
> It seems like if a 401 or 403 (can't remember which one, but neither is
> working for me) is returned, HttpClient should try again, with the
> credentials that we
Ok, that seems reasonable. However, I'm still confused about the behaviour. It
seems like if a 401 or 403 (can't remember which one, but neither is working
for me) is returned, HttpClient should try again, with the credentials that
were in the URL. This doesn't seem to be happening. Would that
On Fri, 2015-07-10 at 16:10 -0700, Derek Lewis wrote:
> Hi folks,
>
>
> I've been upgrading our software to a more recent (4.4.1) version of
> httpclient, and I've run in to a bit of a stumper. It seems like
> embedding the username/password in the URL isn't working with the
> client that's buil
