简体   繁体   English

使用网络代理凭证的Apache反向代理?

[英]Apache Reverse Proxy Using a Network Proxy Credential?

I'm trying to set up a reverse proxy on Apache 2.2 (Windows). 我正在尝试在Apache 2.2(Windows)上设置反向代理。 I am able to do it on a non-corporate network without any problems. 我可以在非公司网络上完成此任务,而不会出现任何问题。 I am attempting to reverse proxy content from a vendor domain, but keep it under my own domain for SEO reasons. 我正在尝试从供应商域撤消代理内容,但是出于SEO的原因,请将其保留在我自己的域下。

dev.example.com/stuff ===> devstuff.vendor.com dev.example.com/stuff ===> devstuff.vendor.com

However, when I try to incorporate this on my internal network, the Internet Gateway proxy is blocking the request, presumably as I'm not properly authenticating the call to the external domain. 但是,当我尝试将其合并到我的内部网络中时,Internet Gateway代理阻止了该请求,大概是因为我没有正确验证对外部域的调用。

dev.example.com ===> Internet Proxy =X=> devstuff.vendor.com dev.example.com ===> Internet代理= X => devstuff.vendor.com

I've been googling every term I can think of and reading the Apache docs and can't find anything which seems to work. 我一直在搜寻我能想到的每个术语并阅读Apache文档,却找不到任何可行的方法。 I have tried running Apache as a service with a network account which would have access, but naturally, it's probably not trying to use the proxy at all. 我曾尝试使用具有访问权限的网络帐户将Apache作为服务运行,但是自然地,它可能根本没有尝试使用代理。

Is there any way to tell Apache to send external ProxyPass requests to use a specific proxy server, and perhaps a specific username/password as well? 有没有办法告诉Apache发送外部ProxyPass请求以使用特定的代理服务器,也许还使用特定的用户名/密码? I'd love to avoid modifying the proxy or firewall too heavily to accomplish this. 我希望避免过多地修改代理或防火墙以完成此任务。

Thanks! 谢谢!

Never quite did figure out the "with passing credentials" part, but using the ProxyRemote directive, we could pass everything for our devstuff.vendor.com domain through our network proxy. 从来没有完全弄清楚“通过凭据”部分,但是使用ProxyRemote指令,我们可以通过网络代理为devstuff.vendor.com域传递所有内容。 From there, we had a proxy exception put in to allow from our web server IPs without authentication, since this was an approved arrangement anyhow. 从那里开始,我们放置了一个代理例外,以允许我们的Web服务器IP无需身份验证,因为无论如何这都是经过批准的安排。

Though, in hindsight, even after solving this, we ended up backing up one step further and just going straight out the firewall for performance reasons (both for the end user with too many hops) as well as negative impacts to our proxy server. 不过,事后看来,即使解决了这一问题,我们仍然进一步备份了一步,出于性能原因(对于跳数过多的最终用户而言)以及对代理服务器的负面影响,我们只是直接淘汰了防火墙。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM