Tag Info

New answers tagged

0

Squid doesn't support SNI what is written here. So to have in Squid: https://server1.com (cert for server1.com) => http://mylanip1 https://server2.com (cert for server2.com) => http://mylanip2 you have to: Put the addresses on different IPs, because a certificate is assigned to a uniqe pair [IP, port]. Configure Squid like this: https_port ...


1

Figured it out. With Macports you have to explicitly install nginx with ssl support using sudo port install nginx +ssl Stupid, I know - why would you ever install it without, and why would your flag start with +...


1

It's clearly explained in the documentation of proxy_cache_valid directive. Parameters of caching can also be set directly in the response header. This has higher priority than setting of caching time using the directive. The “X-Accel-Expires” header field sets caching time of a response in seconds. The zero value disables caching for a response. If the ...


1

You should never bind your business data to chunks. Chunk size can be changed by proxies, or event by different web servers. Even some proxies based on some heuristics may aggregate the chunks. Your chunk parser (client SDK if you have any or etc.) should be able to parse your data even if each chunk has part of a JSON or 1.5 JSON or multiple JSONs.


0

Ok, I changed it and now is like that: upstream connections.domain.com { server 172.16.0.83:443 weight=100000; server 172.16.0.83:80; } server { listen 172.17.0.14:80; server_name connections.domain.com; proxy_pass_request_headers on; proxy_pass http://connections.domain.com; proxy_set_header ...


0

As a complement to HBruijn's answer, if you opt for solution (3) "ProxyPass", you may have to also use mod_proxy_html to rewrite some URLs in your HTML pages. cf. How to handle relative urls correctly with a reverse proxy for some examples. As an applied example, here is how you can configure Apache using the ProxyHTMLURLMap rule to forward everything at ...


0

I would suggest the mod_proxy_wstunnel module available in Apache 2.4.5 onwards. It allows you to relay from a URL to another websocket server on any port. e.g. To take your example: ProxyPass /ws1/ ws://websocketserverA:800/ ProxyPass /ws2/ ws://websocketserverB:801/


0

I've got this working succesfully. By adding login=*:NOPASSWORD I now get a PHP_AUTH_USER variable. The full squid.conf looks like: http_port 3128 accel defaultsite=#### cache_peer #### parent 80 0 no-query login=*:NOPASSWORD originserver access_log /var/log/squid/access.log squid hosts_file /etc/hosts auth_param ntlm program /usr/bin/ntlm_auth ...


2

You'll need to clarify what you're trying to achieve. With a reverse proxy, the user connects to only the abc123.com server. When they request something within /blog, the abc123.com server makes a connection to the abc123blog.com server, makes a request, gets a response, then feeds that response back to the user. If you're trying to encrypt the user's ...


0

You are passing the initial request Host header sub.example.com to example.com : proxy_set_header Host $http_host; When proxying the request, it's likely falling in sub.example.com vhost or default vhost, not example.com vhost, depending on your setup. Remove this line.


0

I think the only problem is with the proxy_pass directive. You mention http://chocolate.company.com where you should in fact use the upstream group name here. I changed the name of the upstream group to better document the change: # this is where all requests should be proxied to upstream chocolate_upstream { ip_hash; server 192.168.10.100; ...


1

This configuration will do what you want: server { listen 80: server_name example.com; return 301 https://$server_name/subdirectory; } server { listen 443; server_name example.com; location = / { return 301 https://$server_name/subdirectory; } } The = / specifiers means a full match, so it matches only the exact root ...


0

Obviously it won't work if you don't exclude location subdirectory from this behaviour for the ssl vhost. server { listen 80; server_name example.com; return 301 https://$server_name/subdirectory; } server { listen 443 ssl spdy; server_name example.com; location /subdirectory { # Your stuff } location = / { ...


3

Apache would see the IP address 192.168.0.123 as the source and that needs to be added the RPAF_proxyips directive, this tells mod_rpaf that its a known proxy. Quoting from http://www.stderr.net/apache/rpaf/ It changes the remote address of the client visible to other Apache modules when two conditions are satisfied. First condition is that the remote ...


1

For nginx-to-apache in same host and single public IP address (for example 192.168.99.1), there are several available options: Nginx listen on 192.168.99.1 port 80 and and Apache listen on 192.168.99.1 on other ports except 80 (for example port 8080) Nginx listen on 192.168.99.1 port 80 and and Apache listen on 127.0.0.1 on port 80 (the same port) The ...



Top 50 recent answers are included