ProxyRemote with authentication

[tomk_41]

Hello,

I try to configure ProxyRemote with a web proxy wich need authentication.

Do you know if something like that is possible :

 ProxyRemote http http://login:[e-mail]:80 

I've got a "407 Proxy authentication required" if I leave that :

ProxyRemote http http://my.proxy.com:80

Is it possible to configure apache in order to send login and password to the proxy ?

Thank you,
Thomas

[jdMorgan]

I don't know, but if your efforts to get this working fail, you could use Satisfy any (see Apache core Satisfy directive and Apache mod_access Allow and Deny directives) to accept connections from the front-end host's internal network address without requiring authentication on the back-end application server.

Jim

[tomk_41]

It's not possible to change front-end proxy configuration.
I have no acces to it.

Sorry but the only way is to send authentication :(

[jdMorgan]

If you can't change the front end, then there is no way to send auth info anyway, because it is the front-end that has to send it. You'll need to get access to the front end server to address this problem, or disable authorization requirements on the back-end.

Jim

[tomk_41]

Sorry. I explained my problem badly.

My proxy with no authentication is the front-end.
It's the back-end, with internet control, which need authentication.

I reversed between front and back in my message.....

I have no acces to back-end proxy.

[jdMorgan]

Now I'm confused. The "front-end" is usually the internet-facing machine, and reverse-proxies requests to the "back-end" either on a point-to-point private network, or on a local area network. The front-end usually presents most "Web pages" to visitors, while passing some requests to the "back-end" for processing by applications hosted on that back-end.

This is the typical scenario in a "reverse proxy" "application server" set-up -- The back end appears as sort of an "extension" to the front-end machine, but is not directly-accessible (or visible) from the Web.

It appeared to me that you were trying to include the auth info in the URL passed from the front end to the back end, with the back-end host being the one that required authorization.

The descriptions of machines and their roles in the Apache mod_proxy documentation may be helpful to you in figuring out this problem.

Jim