Tag Info

New answers tagged

0

Obviously the question is quite old but doing this is possible if you're willing to reconsider your chosen web server. Obviously you already have a Windows Server 2012R2 server so, in order to reduce complexity, there's no reason why you can't use IIS 8.5 to host your https site. I actually use this myself along side an SSTP VPN but I've also given you ...


0

Thank you all for your time to answer. Basically what I'm trying to do is to proxy the outgoing/originated traffic of the 2nd container (NOTE: I'm NOT trying to proxy the incoming traffic, so cannot use the Apache mod_proxy or Nginx proxy_pass. These modules works for incoming traffic). 1st container runs a proxy service on port 8080. As Thierno suggested I ...


0

I think that using the $http_proxy env var should help. You can set an entrypoint in your docker file (for the container #2) to export the env var when the container is starting. Somewhere in your entrypoint, you should have something like this: export http_proxy=http://$CONATAINER1_PORT_8080_TCP_ADDR:$CONATAINER1_PORT_8080_TCP_PORT I don't know exactly ...


0

This is absolutely possible, and does not require Apache on the proxy server to have an SSL key as you say (as the interaction with that server is carried out via HTTP). You essentially just need to use a fairly basic proxy configuration similar to the following as an example: <VirtualHost *:80> ServerName yourintendedname.com ...


1

I have established what the problems were with my setup. 1) SELinux was preventing me from connecting upstream. I have now disabled this and will consider setting it up properly later 2) proxy_pass was doing its job as expected, however the args I needed were http://123.123.123.1:$server_port/$uri$is_args$args; 3) proxy_set_header Host $host correctly set ...


0

If you want people to connect to your server but don't want them to know your IP address then setting up a proxy server somewhere that will forward the traffic to you is the only thing I can think of.


0

You want to maintain the port, then you should put it in proxy_pass. server { server_name bob.something.com; listen 41001; listen 41002; listen 8080; location / { proxy_pass http://123.123.123.1:$server_port$uri; proxy_set_header Host $host; } } You have to realize that this will proxy request through ...


0

Internet explorer and Google chrome both shares same proxy settings. So if we change setting in internet explorer, then it also effects in Google chrome. We can change proxy setting from CMD (command line prompt). Disable proxy setting: @ECHO OFF REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyEnable /t REG_DWORD /d 0 /f ...


0

Reciprocal linking isn't something docker has, so far as I know ( info revealed at run time about a container back ported or reciprocated to a progenitor). That's probably why most tutorials have a third, common ancestor, 'proxy' being used. If you're willing to use frameworks like fig or weave, that I believe have yaml or json configuration files, you'd ...


0

This is very possible, and quite easy with something like HAProxy. Your fontend/backend config would look something like this. frontend http-in bind *:80 mode http option forwardfor acl isServer1 hdr(host) -i server1.mydomain.com acl isServer2 hdr(host) -i server2.mydomain.com use_backend server1 if isServer1 use_backend server2 if ...


0

From nginx's documentation : If the proxy_pass directive is specified with a URI, then when a request is passed to the server, the part of a normalized request URI matching the location is replaced by a URI specified in the directive. So here this means if you hit http://<domain>/cfbrokerlogs/foo then it will be forwarded as ...


0

As you mentioned. while Varnish does not handle SSL it is possible to use a SSL termination proxy which passes to Varnish. The SSL termination proxy can add or remove headers and change ports so you should be able to create a flow that avoids redirect loops. Popular SSL termination proxies are Pound, Stunel, Nginx and HAProxy. The range of features you ...


2

If a company has every client and server on a single subnet, then yes.. clients could potentially be without a default gateway, if they are using a proxy. Not all applications are proxy-aware, so I would call it a horrible, horrible setup. But yes, it is possible.


-1

As far as I can tell you just want a transparent http proxy? http://www.tldp.org/HOWTO/TransparentProxy-6.html


0

You simply can't do this with a iptables alone and a http proxy like squid, because most network protocols simply were not designed with transparent proxy as a feature. They must be explicitly configured to use a proxy. The closest you can get is to use a socks proxy like Redsocks


-1

Your backend responds with < Cache-Control: max-age=2592000, public, must-revalidate, proxy-revalidate < Expires: Sat, 14 Feb 2015 19:33:58 GMT So does the original answer, and this overrides the proxy_cache_valid setting: Parameters of caching can also be set directly in the response header. This has higher priority than setting of caching time ...


0

Don't use Rewrite for this, use a simple proxy. It seems you need something described here.


0

The important thing to understand is that the SYN-cookie allows the server to respond to the initial SYN without creating a flow-table entry; it uses up way less ressources and keeps your server online; performance increases of up to 20x are common! You should really read these background articles; SYNPROXY is really worth a try. ...


1

This should be all you need: RewriteEngine On RewriteRule ^/api/(.*)$ https://example.com/api/$1 [P,QSA,L] Apache will basically proxy your requests by creating new http requests via the mod_rewrite module, which is enabled by default


0

Yes, you can. http://nginx.org/r/proxy_pass As you can see from the description of the proxy_pass directive, it allows redirection for both http and https protocols / address schemes. I would imagine that you can even setup a general-purpose TLS interception device with nginx, through the use of proxy_pass $scheme://$http_host;. Additionally, you might ...


0

Not easily. By default, HTTPS connections are encrypted and you can't pass them through a proxy... what you could do is filter them by the destination IP, by allowing only some addresses and denying everything else using the firewall; however some servers use virtual hosts and host different websites under the same IP, so if the same server hosts both a ...


4

My bet? lighttpd is adding an X-Forwarded-For header, and Django has something hardcoded somewhere to know that 127.0.0.1 is unlikely to be the real remote IP address if that header's present. You should verify that the X-Forwarded-For header is present, then get Django to use that as the remote address (looks like the way to do that is here).


0

I got the same behaviour with Squid 3.3.8 (package up to date on Ubuntu 14.10 at the time of writing) After digging here, I found out that the cache mishandling of CSS and JS when the Vary Header is present was effectively a bug, fixed in posterious releases. Installing Squid 3.4.10 from the sources, makes disapear this issue.



Top 50 recent answers are included