Tag Info

New answers tagged

3

You've answered your own question already. Yes, That's what ICP is for. What you need to do next is read up on ICP. "I don't know anything about ICP" is not a good question for serverfault, but by all means come back with more specific questions once you've made a start.


1

The Winfrasoft one is 4,500 per server. Try a free, open source one: https://github.com/ramonsmits/XFF-Filter4TMG


0

The index directive is causing an internal redirect to /index.html, so it's getting matched by your location / block. You'll need a separate location block to handle /index.html and make sure it doesn't get matched by the location / block. If you have any other static resources like images or CSS used in index.html, you'll want a location block to handle ...


0

Please clarify - what do you want. At first - iptables work only with packets. It can't set user and password for proxy. But you can set redirect traffic from each VM(it's ipadress) to each own proxy server. I think iptables -t nat -A PREROUTING -i eth0 -s vm_ipaddress -p tcp —dport 80 -j DNAT —to proxy_ipaddress:port should help you.


1

You can use mod_rewrite.c to redirect a request to https. Though make sure you don't enable SSLEngine on the page you want to redirect from. In this example I'm redirecting all traffic coming in to test.mydomainintereactive.com on port 80 to test.mydomainintereactive.com on port 443 (standard https port) <VirtualHost *:80> ServerName ...


0

update for anyone that may find this thread; the openldap documentation is extremely lacking for proxy setup. This was found by basically 48 hours of trial and error. note: I switched back to slapd.conf by adding the following in /etc/sysconfig/ldap SLAPD_OPTIONS="-f /etc/openldap/slapd.conf" In the slapd file you will find 4 databases; 1. local ...


1

There are a few articles regarding this configuration here and here. We also use client SSL certificates with Nginx and have the following working config with http/https redirect : #config for upstream app servers (not aware of SSL) upstream appcluster { server X.X.X.1:8000; server X.X.X.2:8000; } # http-to-https redirect server { listen ...


0

This may not be what you're wanting, but you could set up another Apache proxy such as in a virtual machine and modify the /etc/hosts file there. Then traffic would travel through two proxies - the one you have now followed by the one you set up on the virtual machine. Not ideal I know, but a possible solution if nobody comes up with something better. ...


0

You will have to rewrite using mod_rewrite, or configure the application to create proper urls.


1

It's a relatively basic configuration -- just load mod_deflate and configure it (SetOutputfilter, AddOutputFilterByType, etc) as the manual for mod_deflate describes.


3

proxy_http module requires proxy, and ProxyPass directive is defined in the latter. Make sure it's also loaded.


1

In the default Apache configuration, the AllowEncodedSlashes directive is set to off. This means that: "...The AllowEncodedSlashes directive allows URLs which contain encoded path separators [...] to be used in the path info. With the default value, Off, such URLs are refused with a 404 (Not found) error. ..." So the problem is that mod_proxy is not ...


0

While this question is quite old and the answer is correct, after some digging to resolve my own load balancing problem I found that there is a newer option to make the client ip based on the X-Forwarded-For or X-Real-IP and when combined with the ip_hash directive it properly balances load using the user's actual IP as the hash. ...


0

I think it has this behaviour because in http:// the / is still seen as directory separator. Thus you're looking for the resource paramater.org under folder http: (by folder, I don't really mean a real folder as it could just be an access path but you can get the point). I don't think you can juste type / for a resource in an URL, so you have to use %2F


0

ssh host2 sed -i~ ' /Proxy/s/[IP of server 1]/[hostname of server 1]/ ' /etc/httpd/conf/httpd.conf Please read on the mechanism and especially the reasons whereby changes to files marked Config in RPMs will not receive any [security] updates if they've been modified. This was recently(-ish) a problem with a security update ostensibly delivered to ...


1

There is a workaround for this. Idea is to make a proxy server block for each upstream. upsteam api_servers { server 127.0.1.1; server 127.0.1.2; server 192.168.1.3; } server { listen 127.0.1.1; location / { proxy_pass http://192.168.1.1/api/; } } server { listen 127.0.1.2; location / { proxy_pass ...


0

A client cert won't work, because the device won't know to provide it. What's wrong with just using the source IP? You can correlate that to a device, long-term, with the DHCP logs and MAC address.


3

Your problem is that browsers don't even send the fragment identifier to the server, so even if Nginx was willing to rewrite based on that, it wouldn't be able to do so because it wasn't provided with that info. I'm really curious about how your previous solution worked with Apache - I just double checked and my Firefox doesn't send the fragment identifier ...



Top 50 recent answers are included