reverse-proxy

Reverse proxy OpenVpn using Haproxy or Nginx

吃可爱长大的小学妹 提交于 2020-01-25 07:37:06
问题 i was wondering how it is possible to reverse proxying an openvpn connection using the SNI, i've read so much about that: HERE and HERE I've tried any kind of solution, using haproxy and using nginx, but it seems that my client (i've tried Tunnelblick and a simple openvpn client on linux) does not send the SNI information Basically, this is the result that i want to achieve: vpn1.app.com ─┬─► *.app.com dns -> nginx at my public ip ─┬─► vpn1 at 10.0.0.3 vpn2.app.com ─┤ ├─► vpn2 at 10.0.0.4

reverse proxy with nginx ssl passthrough

社会主义新天地 提交于 2020-01-24 20:37:40
问题 Dear all I have following situation. I have several ISS Webservers hosting multiple web applications on each IIS server. The do have a public certificate on each system. Every IIS has an unique IP. All IIS Server are placed in the same DMZ I have setup an nginx System in another DMZ. My goal is, to have nginx handle all the requests to the IIS from the Internet and JUST passthrough all the SSL and certificates checking to the IIS. So as it was before nginx. I don't want to have nginx break up

Can you use nginx reverse proxy to docker containers without exposing any ports?

余生颓废 提交于 2020-01-23 03:25:27
问题 I'd like to know if it's possible to use nginx with docker compose as an api gateway / reverse proxy / ssl termination point without exposing any ports on the containers behind it. I.e. I want to use only the intranet created by docker compose when the containers are linked to communicate past nginx. Ideally the only publicly accessible port will be port 443 (ssl) on nginx. Is this doable? Or do I have to expose ports on my containers? 回答1: Yes is doable. Just define your application in one

Flask redirect(url_for) error with gunricorn + nginx

感情迁移 提交于 2020-01-22 09:09:31
问题 I am having a problem with the redirect(url_for) function in my flask app. Any redirect(url_for("index")) line redirects the application from domain.com/app to ip-addr/app , where the ip-addr is my own client machines ip, not the server's. This has gotten me very confused, and I don't know where exactly the issue occurs, as it only happens on the server and not on any local testing. Details: I am using the reverse proxy setup found here http://flask.pocoo.org/snippets/35/. My nginx config is

Service fabric service discovery without port number

℡╲_俬逩灬. 提交于 2020-01-16 14:53:05
问题 I have a service fabric cluster hosting legacy WCF services. Each of the WCF services is allocated a port number and uses the net.tcp protocol. I wonder what is the best way for service discovery and auto-scaling? I tried service fabric's DNS service and let service fabric assigns the port number for each service, however, the client won't know about the dynamic port number. The DNS service can only resolve the ip-address based on service DNS name. Since each service is on a specific port, I

Properly mount Flask app at location using Nginx reverse proxy

时光怂恿深爱的人放手 提交于 2020-01-15 09:29:50
问题 I have a Flask app, which runs inside a Docker container and should be exposed under a specific URL: myserver.com/mylocation . I want to use another container running Nginx as a reverse proxy to achieve the routing. I am following an awesome tutorial that got me quite far already. My Nginx-config (the relevant part) reads: server { server_name myserver.com; location /mylocation { proxy_pass http://myapp:5000; proxy_set_header Host $host; rewrite ^/mylocation(.*)$ $1 break; } } My docker

Maintenance page forwarding with htaccess does not work for proxied material

别等时光非礼了梦想. 提交于 2020-01-15 06:55:47
问题 I have scoured the internet and am at a loss as to why my maintenance page redirect and rewrite rules do not work for any proxied material or anything that is coming across through https. I am using an Apache 2.2.3 server with tomcat 6.0.24 installed on it. I have the following htaccess file: Options +FollowSymlinks RewriteCond %{REQUEST_URI} !/maintenance.html RewriteCond %{REQUEST_URI} !/images/(.*)$ RewriteCond %{REQUEST_URI} !/scripts/(.*)$ RewriteCond %{REQUEST_URI} !/styles/(.*)$

Maintenance page forwarding with htaccess does not work for proxied material

末鹿安然 提交于 2020-01-15 06:55:26
问题 I have scoured the internet and am at a loss as to why my maintenance page redirect and rewrite rules do not work for any proxied material or anything that is coming across through https. I am using an Apache 2.2.3 server with tomcat 6.0.24 installed on it. I have the following htaccess file: Options +FollowSymlinks RewriteCond %{REQUEST_URI} !/maintenance.html RewriteCond %{REQUEST_URI} !/images/(.*)$ RewriteCond %{REQUEST_URI} !/scripts/(.*)$ RewriteCond %{REQUEST_URI} !/styles/(.*)$

Cache-control: Is it possible to ignore query parameters when validating the cache?

放肆的年华 提交于 2020-01-15 03:33:11
问题 Is it possible to set a cache-control header communicating with a reverse proxy to ignore query parameters in determining what is a unique uri or in short: validate a cache even if some query parameters have changed? Sometimes query parameters have nothing to do with the rendering of the page at least from a server side perspective. For instance all utm_* variables from Google Adwords. These are needed for the javascript on your page so you don't want to strip them away and redirect to a

WebService behind reverse proxy

旧时模样 提交于 2020-01-14 03:20:52
问题 I have a web service which is behind a reverse proxy. Now what is happening is when I try to add a web reference to test the web service then it says that it is unable to download the wsdl file. That is because when the request is sent it it is https://uat.mywebservice.com/Service/Service.asmx but when it hits the reverse proxy and then tires to download the wsdl and disco files it changes the link to http://myservice.comp.com/Service/Service.asmx?wsdl and it this is not the right link as