Hi all,

I'm currently trying to get Mongrel running my app whilst fronted by
apache 2.2 in a sub-directory via https.  A bit convoluted I'll grant
you but necessitated by existing systems.

The pertinent parts of my httpd.conf:

<VirtualHost 123.123.123.123:12345> #historic choice of random port number

DocumentRoot    /var/www/admin
ServerName      admin.example.com:12345

ProxyPass /rails  balancer://proxy_group
ProxyPassReverse /rails  balancer://proxy_group

<Proxy balancer://proxy_group>
    BalancerMember http://127.0.0.1:3000
    BalancerMember http://127.0.0.1:3001
</Proxy>

SSLEngine on
...
ssl config continues
...
</VirtualHost>

I've seen in a few places [1][2] that the trailing slash is important
on the ProxyPass directive but if I include that then I get a BAD
CLIENT error in mongrel due to too many  slashes:

BAD CLIENT (127.0.0.1): Invalid HTTP format, parsing fails.
REQUEST DATA: GET //admin/list_returns HTTP/1.1

The two main problems I have now is that all rendered links are
missing the sub-directory and if any redirects are issued then they
are for http://admin.example.com:12345/ instead of the ssl version
https://admin.example.com:12345/ - is this because mongrel/rails is
only seeing a http request?  And if so is it possible to let the app
know that it's actually https and in a subdirectory?

Paul.

Mongrel version: 0.3.12.4
Server version: Apache/2.2.2

[1] - http://textsnippets.com/posts/show/400
[2] - 
http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel

_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to