Hopefully this is the correct channel for such a question and my quest for further knowledge.
I've currently built a significant platform which allows clients to communicate with our API
, which in turns allows "items" to be pushed to a print queue.
Most third party developers and app users have no problem consuming the API
, and I only assume this is because they authenticate
over basic auth
outside a proxy
environment.
We have one client, that appears to be locked behind a proxy
of sorts, which prevents the consumption of a particular endpoint
. I'm regrettably faced with the 407 - Proxy Authentication Required.
I'm very keen to understand is this something the end user (client) should resolve by adjusting proxy security settings (if needed) or a developer problem?
I'm also keen to understand what is actually happening? End user behind proxy
calls the API
, to try and authenticate via basic auth
, and then tries to authenticate via proxy-authenticate?
Ideally not looking for a fix but more knowledge on what is happening, so I can fix myself.
client
, you meancustomer
orhttp client
(app)?