Tag Info

New answers tagged

1

I found that stunnel may be a suitable solution to add that layer in between, is it a good solution? I don't aware that nginx have that functionality (i.e. provide client certificate when proxying request to upstream). The stunnel solution works in this case. You can provide certificate per service. Configure it in stunnel.conf [upstream] accept = ...


0

I had the same issue on Windows 2008 R2 with WPAD record. To fit it we add fake DNS record to hosts file like 1.1.1.1 WPAD and after restart the update client it stop using proxy. In some cases the Server needs to be rebooted after WPAD block. Cheers, Andrey


0

On a global proxy level I've done it using session cookies like this: <Proxy *> Order deny,allow Deny from all SetEnvIf Cookie "authtoken=myCookie" let_me_in Allow from env=let_me_in </Proxy> You may be able to restrict access to individual directories based on cookies using explicit URLS in the Proxy config like this: <Proxy ...


1

So, my question is - how do I put http://www.baidu.com instead of / (SLASH) in GET request? The request you want to have is not a bad one, but just a proxy request. To create it just specify your target host as a proxy. Apart from that curl might be not the right tool to generate real bad requests.


1

What that's likely doing is checking the Host header that your web browser is sending to determine what domain to proxy to (and using wildcard DNS to make all the subdomains under their domain go to their server). That part's easy, but translating any resource requests to also use the proxied domain is a much trickier problem to solve. Something like ...


1

It would be pretty trivial to setup: Multiple wildcard A records (*.unblocksit.es, ..unblocksit.es, ..*.unblocksit.es, etc) - so any request goes back to their webserver. Apache config or PHP script that reads the requested URL, strips off the end, and proxies the content.


3

To start, I would set up Nginx as a reverse proxy to the third-party server. You can read about how that works here: http://nginx.com/resources/admin-guide/reverse-proxy/, an example setup might look like: server { listen 80; server_name example-proxy-domain.com; location /some/path/ { proxy_pass ...


1

GitHub encourages forking. The Git repository you cited is a fork that differs from your Debian package. Assuming that you are using libapache2-mod-rpaf for Debian wheezy, inspect libapache2-mod-rpaf_0.6-7+wheezy1.dsc. Format: 3.0 (quilt) Source: libapache2-mod-rpaf Binary: libapache2-mod-rpaf Architecture: any Version: 0.6-7+wheezy1 Maintainer: Sergey B ...


-1

Documentation is here: https://github.com/y-ken/mod_rpaf https://github.com/gnif/mod_rpaf Example Configuration LoadModule rpaf_module modules/mod_rpaf-2.0.so RPAFenable On RPAFproxy_ips 192.168. 10.0.0 RPAFheader X-Forwarded-For RPAFsetHostname Off RPAFsethttps Off RPAFsetport Off I dont know Why they remove the ...


-1

Your PEM file is not the correct format. Checkout this post. http://projectzme.wordpress.com/2013/02/02/tip-sslproxymachinecertificatefile-returns-missing-or-encrypted-private-key/


1

You'll do much better to simply use a network device that can do outbound load balancing, based on sessions, percentage of bandwidth used, etc. I'm answering your question as if it was a request for info about a technology, rather than an explicit product request.


0

Edit the file /etc/datastax-agent/datastax-agent-env.sh and append the follow line: JVM_OPTS="-Dhttps.proxyPort=<PROXY_PORT> -Dhttp.proxyHost=<PROXY> -Dhttps.proxyHost=<PROXY> -Dhttps.proxyPort=<PROXY_PORT> Restart the Agent /etc/init.d/datastax-agent restart


1

covener is correct, mod_proxy is not able to do this. However, Gor was written to do exactly this. Hat tip to Arthur Lutz for posting the answer here.


1

It tells you that the URI in the proxy pass directive can't be used in a regex location. This is because nginx can't replace the part of the URI matching the regex in the location block with the one passed in the proxy_pass directive a generic way. Simply imagine your location regex is /foo/(.*)/bar, and you specify proxy_pass http://server/test, nginx ...


0

The message is quite clear: proxy_pass doesn't work in a location specified by a regex. You have to make this four rules instead of two in that case. See the doc for more options.


2

No, Apache's mod_proxy simply cannot send a request to multiple origin servers.


1

Perhaps an easier solution is to have it all running on server1 and just tunnel pop/pops and imap/imaps to server2 (autossh is a simple solution, but there are probably some better ways). If you run autossh to maintain a ssh connection from server2 to server1: autossh -M 3319 -4 -R 993:localhost:993 -R 995:localhost:995 -NC server1 -f You could throw ...


1

A couple of possible solutions: Stand up Dovecot on server1, and configure it to use login referrals to send the clients over to server2. If your clients support login referrals, this could be the simplest solution. It would introduce a small delay with each new login, as the client connected to server1 and then got sent over to server2. Stand up Dovecot ...


0

In my case it was firewall default policy which was set to "DROP". You need to check which port is being listened (usually it is 6000 + value in $DISPLAY environment variable) and set proper rules. Run as root: # echo $DISPLAY localhost:10.0 # netstat -altnp | grep LIST tcp 0 0 127.0.0.1:6010 0.0.0.0:* ...


0

I have solved this on my own after a bunch more research. I had a rewrite script set that I forgot I set, and said script was crashing on 90% of URLs. Fixing the script fixed this issue.


0

Set a ProxyTimeout to just a few seconds - what's happening is that it's sitting there trying connections to the down backend for a long while, not timing out. Setting something like ProxyTimeout 3 will cause the connection to fail more quickly, then your retry=60 setting will cause the down server to not be used again for the next minute.


1

Well, what you want to do is called proxying, so maybe what you meant was to make Squid invisible and disable any caching features ? If so, disable caching by removing all cache_dir and refresh_pattern directives from the configuration file, and add the following to make the proxy invisible to the eyes of the web servers : forwarded_for transparent via off ...


0

Create an ACL for the domain(s) you want to exclude from the log : acl exclude dstdomain abc.com For multiple domains you can use a separate file, and have one domain per line in it : acl exclude dstdomain "/etc/squid/excluded.txt" Then, disable logging for that ACL : access_log none exclude



Top 50 recent answers are included