Tag Info

New answers tagged

-1

I am also facing the same issue that is unable to keep session. Cesar has mentioned that he has resolved the issue with apache but I am getting the same even with apache. Can someone pls help me. I have did the following setup. DNS Configuration subdomain.mydomain.com 10.10.10.10 Proxy configuration in apache at 10.10.10.10 <VirtualHost *:80> ...


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

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

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 ...


0

Use Rewrite conditions to match for this special case: RewriteEngine On RewriteCond %{REQUEST_URI} ^/socket.io [NC] RewriteCond %{QUERY_STRING} transport=websocket [NC] RewriteRule /(.*) ws://localhost:8082/$1 [P,L] ProxyPass /socket.io http://localhost:8082/socket.io ProxyPassReverse /socket.io ...


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; }


0

I had the same problem and I finally solved it by using two levels of proxy. Here is how you could do for your situation (I think): server { listen 8001 default_server; server_name web1.example.com; location / { proxy_pass http://web1.local:80; ...


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; }


0

Turned out not to be a problem with the nginx conf - that was fine. The problem is due to the fact that Chrome only allows setting of cookies from fully-qualified domain names, not for IP addresses https://code.google.com/p/chromium/issues/detail?id=56211 I bought a domain name, applied it to my server, and it worked. It required one change to the nginx ...


0

You have two options: Option 1: Keep the DNS as is.Setup a redirect on Apache.Make sure to exclude your reverse proxy so it doesnt get redirected to itself. Advantage is that this is less effort. Option 2: Move stuff around. Create an additional A record, say blog-backend.example.com pointing to the server actually hosting the blog (Apache) Change the ...


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

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


0

I use this with Jira in apache. Note: I use the /jira which I configured in jira/conf/server.xml (see below). Also note proxyName="example.com" <VirtualHost *:80> ServerName example.com Redirect permanent / https://example.com/jira/ </VirtualHost> <VirtualHost *:443> ServerName example.com Redirect ...


1

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


0

You can enable sticky session or session affinity. This will ensure that the requests from same client are passed to the same tomcat every time Change in nginx: sticky cookie srv_id expires=1h domain=.example.com path=/; http://nginx.org/en/docs/http/ngx_http_upstream_module.html#sticky


0

I did it for Microsoft Exchange with ntlm passthru auth and MSExchange RPCoHTTP/HTTPS on CentOS 6. I've used: HTTPD 2.4.10 mod_proxy_msrpc These are the steps I did: yum -y install gcc make patch pcre-devel openssl-devel libuuid-devel cd wget http://www.apache.org/dist/httpd/httpd-2.4.10.tar.gz wget "httpd-2.4.10-deps.tar.gz" tar xzvf ...


0

The problem: The login form posts to the URL Drupal knows about: /proxy. That means that the proxy server receives a request for http://c5.domain.com/proxy, instead of http://c5.domain.com/my-account. I thought I could solve this with a redirect: RewriteRule ^/proxy/(.*)$ /my-account/$1 [R,L] RewriteRule ^/my-account/proxy/(.*)$ /my-account/$1 [R,L] As ...


0

Try adding the following to your HTTP connector in the Jetty application: <Set name="forwarded">true</Set> This will try to read the following headers that are supposed to be sent by the proxy: X-Forwarded-For - The IP address of the client X-Forwarded-Host - The original host requested by the client in the Host HTTP request header ...


-1

So the issue was actually with Zend Framework BaseUrl setting. I have removed it, and everything is working now.


0

Update ProxyPassReverse as below. ProxyPassReverse /myapp http://ext-domain/myapp Refer: http://httpd.apache.org/docs/2.2/mod/mod_proxy_ajp.html#usage


1

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


0

I can't quite get the server to 403 everything in /error/ externally, but I managed the runner-up: to 403 everything not otherwise available. I had to use rewrite to get it to work, because without it, a request to /error/ alone would give the default nginx error message, and not the custom one. That I still can't figure out. server { server_name ...


0

Try using a fallback director There are several directors in Varnish, the fallback director will start to use an endpoint only if the others are considered dead.



Top 50 recent answers are included