similar to: Auth before proxy

For some users, request.remote_ip always return nil. According to the RAILS''s help: REMOTE_ADDR is the standard but will fail if the user is behind a proxy. HTTP_CLIENT_IP and/or HTTP_X_FORWARDED_FOR are set by proxies so check for these before falling back to REMOTE_ADDR. HTTP_X_FORWARDED_FOR may be a comma- delimited list in the case of multiple chained proxies; the first is the

Hi all, I''ve just spent some time going through trying to get mongrel & apache 2.0 working with mod_proxy. I thought I''d share what I''ve found in case someone is going through the same exercise. Of late, I''ve been using mongrel (lovely, btw) to run my rails apps. Since I have a couple of different rails apps running on the machine, I thought it be nice to

Hello all, For the last couple of days I was trying to get my Apache/mod_proxy/mongrel setup to limit the size of the request body. The setup is as follows: 1.) Apache acts as a reverse proxy by facilitating mod_rewrite and mod_proxy 2.) Requests for non-static files are passed on to a mongrel_cluster 3.) We use mongrel for our Ruby on Rails application Note that due to some restrictions we are

I''m running Apache 2.0 as a proxy to several Mongrel/Rails apps, so that all of my Mongrel apps can be routed through the single Apache IP address. Apache 2.0 is already in use on the system, which is why I haven''t decided to use Apache 2.2. The problem I''m having is that this setup only works for Rails apps that do not use the public/index.html file as the main

Hi mongrel-users, Just a heads up for apache2.2 mod_proxy + mongrel + rails users: If you have a line like this in your source (because you''ve done a poor job maintaining your code and reading the API docs): render ''foo'', :layout => ''bar'' You might expect it to do what it says... but it actually sets deprecated_status and ends up setting

Hello, still trying to get things going. With proxypass the REMOTE_USER variable set by mod_auth_* is not passed to mongrel. I found another admin that has the same problem[1], but no solution. Did someone here solve this problem? [1]http://mail-archives.apache.org/mod_mbox/httpd-users/200610.mbox/<323a37200610021509k6142cb08q6e6b0642e3261c6d%40mail.gmail.com>

I was able to find some information about this in the list archives, but it ended with a possible patch being submitted for Mongrel. I tried to follow a few of the instructions, but I''m still kind of stuck, since I''m not sure if what I''m seeing is the proper results. I have an application running on a cluster of mongrel servers, which is behind pen, which in turn is

I am trying to run a Typo app behind on mongrel, with Apache proxying on Windows XP. The idea is to have the subdirectory /ebway point to my app. I am using the following code in my http.conf: LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so ProxyRequests Off <Proxy *> Order deny,allow Allow from all </Proxy>

Hi, I''ve got to active project both running on the last Apache 2.2 and on Mongrel 0.3.13.3. One is running perfectly, the other gets (always on the same pages, but not after each request, it seems to be random) a ProxyError every now and then which leads to the mongrel process being called to die and subsequently slowing down the whole web site. I have to restart the mongrel

Hello all. I currently have a couple of simple semi-official intranet sites running on a computer at work (I shanghai''d it to run these sites along with it''s primary purpose). Each site is running on one mongrel server that hosts the ruby/rails app. One is running on port 80 and the other is running on port 81. What I am after is a super simple WINDOWS compatible program

I am trying to move a Rails application, that uses SSL, from an Apache/FastCGI stack, that works fine, to Apache22 and mongrel working with a single mongrel instance (i.e., not mongrel cluster, yet.) I have a single mongrel instance demonized and working fine on http, on port 3000. Apache/OpenSSL/certs working fine. Here is my test http.conf (deliberately kept as simple as possible):

Hi Guys, I know this is slightly off topic, but it''d be great to get some feedback from anyone who''s using mod_proxy on Apache 2.2 to redircet to a rails app on mongrel. Everything has been running fine generally but a few days back we started getting a gap in the performance between the Apache port and the mongrel port. accessing through port 80 was averaging ten times longer

This is not directly a Rails question but you lot seem the best to ask... I have a strong feeling we will be developing future apps in Rails (Ruby fans are slowly starting to outnumber cynics in my office) so I want a web server plan that will be appropriate for that. We have just bought two new web servers I want to turn into a load-balanced, redundant pair. As well as any Rails

Hi Guys, I hope its ok to post to this list. I have a rails on ubuntu deployment stack which consists of: locally: cap 2.3.0 and all latest deps server side: apache 2.3, mongrel_cluster, mod_proxy and git on the same host. I am connecting to my remote host via ssh with agent and pass phrase. All is good until my first mongrel task, deploy:restart task. I have included the

I''m running Apache 2.0 as a proxy to several Mongrel/Rails apps, so that all of my Mongrel apps can be routed through the single Apache IP address. The problem I''m having is that this setup works well for apps that do not use the public/index.html file as the main page. For any apps that do use public/inedx.html as the main page, none of the links off of index.html work. So no

I am running a Mongrel cluster with an Apache front-end. I am loading the following modules in the httpd.conf file: LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_connect_module modules/mod_proxy_connect.so

Updates the installer to handle the scenario in which the guest and admin networks are the same by using an alternative httpd conf. Verified to work (eg oVirt managed vms are bootable) on the oVirt appliance so far. --- conf/ovirt-server.conf | 88 -------------------- installer/bin/ovirt-installer | 11 +--

There is a big difference if you are not running a pure rails site. I am doing auth apache-side because I serve static content, perl scripts via cgi and feed the mongrel pack from Apache. The REMOTE_USER variable value can be passed to rails using a technique described deep down in one of the informative pieces on the Mongrel website. Bill On Mon, 12 Mar 2007 17:54:07 -0700, Matte Edens wrote:

Hello All I am trying to install 5 mongrel servers against my app. i am using Vista. I found this article on a website.. but am stuck on one point. here are some notes from article: Now enable the needed modules (url rewriting, proxy, proxy_balancer e proxy_http) by editing the httpd.conf file (under c: \Apache_Software_Foundation\Apache2.2\conf, if you installed Apache in its standard path).

Hello, I want to install a mongrel rails server with an apache in fronthead, all that on OpenBSD. But OpenBSD is released with a homemade Apache 1.3.29 patched by the OpenBSD team. I really want to keep this version of apache and I don''t want to change it to Apache 2.x (because of the security and the license but it''s not the point here). But for having mongrel, it has to be with