Show all posts by user
Anything related to migrating to nginx, including rewrites
Re: Location header rewriting needed - 10 years ago
After some time I found what's causing the problem. A trailing slash was missing on the URI part: location / { proxy_pass http://<server1_ip>:7777 } location /server1/ { proxy_pass http://<server1_ip>:7777/; } location /server2/ { proxy_pass http://<server2_ip>:7777/; } However the next problem is that due to the slash "+" characters in my URI get convby Wurstteppich - Migration from Other Servers
Re: Location header rewriting needed - 10 years ago
Some further information: When the Nginx config is running I get 302 FOUND response with the location header as an anwser. However the location answer is pointing to the local domain, means the proxy itself and therefore is looping.by Wurstteppich - Migration from Other Servers
Re: Location header rewriting needed - 10 years ago
Some more information. I now setup a config for Nginx similar to Apache, however it behaves different. The Apache will return the content from the backend server directly, while Nginx ends in an endless loop static "too many redirects" on the browser side at the end. Furthermore I noticed that when I curl -i it I get a "Location" with the URL which I actually try to access in rby Wurstteppich - Migration from Other Servers
Location header rewriting needed - 10 years ago
Hi, currently we run Apache to proxy requests to Java servers running on different machines, but we need to rewrite the header of the requests, means we need a replacement for ProxyPassReverse. Any idea how to do that? Current setup looks like that: <VirtualHost *:80> ServerAdmin <admin_mail_here> ServerName <local_server_domain> RewriteEngineby Wurstteppich - Migration from Other Servers
 |
 |
 |
 |
|