[Bug 37355] Allow to specify Proxy-Authorization in ProxyRemote

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=37355

--- Comment #18 from William A. Rowe Jr. <wr...@apache.org> ---
Thank you for the revised patch.  It is easier for the core developers to read
a small dedicated patch that addresses just a single issue at a time, even if
that means there is a set of several patches to get to the desired outcome.

Here's one proposal that wouldn't require API changes.

If we added a 407 handler extension of some sort, we would be able to handle
specific backend challenges for auth credentials in a unified way.  If we
stored the credentials in an auth challenge table, we could eventually support
other auth methods, including digest or even cookie based auth.

The syntax of the ProxyRemote directive still changes, but the scheme://host
would be split from the auth user:pass and stored in two different mechanisms.

The only downside is whether users in practice would want to identify a
particular proxy use by use case.  While we can keep different stores of auth
tupples by virtual host, further differentiation might prove troublesome.

Thoughts?

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org