Tag Info

Hot answers tagged

4

This IS possible with Haproxy. You can setup a TCP proxy and extract the SNI and do routing based on the SNI. Here's an example: backend be.app1 mode tcp no option checkcache no option httpclose tcp-request inspect-delay 5s tcp-request content accept if { req.ssl_hello_type 1 } tcp-request content reject use-server server1 if { ...


3

Edit: (1) Sorry, some typo here (2) I adjust regex so it matches one or more slash before string mybucket like your log above. Well, maybe you mean something like this location ~* ^/https://s3\.amazonaws\.com/+mybucket(.*) { ... proxy_pass http://s3.amazonaws.com/mybucket$1; }


2

You should learn how Nginx handle location. See this old wiki or new one or this blog. The summary: There are 4 types of location rule, and are applied with the following priorities: Exact matches: There can be only one exact match – the clue is in the name!. For example: location = /foo/bar High priority prefix: There can be more than ...


1

You can use the ! target to prevent a location to be proxied: <Virtualhost *:80> DocumentRoot /path/to/parent/of/phpmyadmin ProxyPass /phpmyadmin ! ProxyPass / http://localhost:2368/ ProxyPassReverse / http://localhost:2368/ </Virtualhost> This will proxy all requests to localhost:2368, except those to phpmyadmin. ...


1

About first part of your question: Update your regular expression. I think you don't need parenthesis in case you have only one extension: location ~* ^.+\.js$ { proxy_pass http://127.0.0.1:8188/filter?source=$1; proxy_redirect off; proxy_buffering off; }


1

There are several tools that handle threat management at different levels (most of them reactive because, being an encrypted protocol, it is hard to see anything until it is written in the logs). SSH is, generally, a secure protocol on its own if configured correctly. I am usually advocating AGAINST letting SSH open to the Internet unless absolutely ...


1

Identifying the type of request and forwarding it based on that cannot be done at the TCP level. By the time your gateway need to decide which host to NAT it to, the request has not been sent yet. On the application layer, you have more possibilities. This will be protocol dependent and is only possible for some protocols. An HTTP proxy is one example doing ...


1

It was indeed a bug, as of now it is fixed, more information on Squid's bugtracker.


1

Try to add this in server config: add_header Cache-Control "no-cache, no-store";


1

You can achieve this functionality by using a standalone cache (e.g. memcached or redis). nginx has modules to work with them. You will need to some convention on cache keys (e.g. construct the key from user cookie and url). In this case, you can control the cache items from the backend, including invalidating and updating.


1

You still need to be using SSL on port 8443 in order to to read the request and make a response.



Only top voted, non community-wiki answers of a minimum length are eligible