WebSetUserAuthBasic with WebCustomRequest?

[David Taggart]

I'm setting a username and password using WebSetUserAuthBasic, but when I make a POST to a URL using WebCustomRequest requiring authentication, I get HTTP/1.1 401 Unauthorized.

Out Headers do not show Authentication Basic either, just:

POST /URL HTTP/1.1
Host: hostname.com
Connection: Keep-Alive
Accept: */*
Accept-Encoding: gzip, deflate
User-Agent:
UA-CPU: x86

[kue]

Hi David,
after a 401 response the request is normally repeated with the Authorization header.
Does your 401 response contain a WWW-Authenticate header field?
Cheers,
Thomas

[David Taggart]

Alas this is a web service I'm attempting to monitor. Authentication must be provided in the initial request. An Authentication header IS included when I'm using WebURL, but not when I'm using WebCustomRequest .

[kue · Accepted solution]

Did you specify the "URL representing protection space for basic authentication" parameter - the 3rd one of the WebSetUserAuthBasic API call in WebUrl and WebCustomRequest?
It works for me with both when I set the protection space url.
Cheers,
Thomas

[David Taggart]

That worked for me, thanks Kue!