On 26 Jun 2013, at 6:33 AM, Martin Weissenboeck <mweis...@gmail.com> wrote: > I have tried routes.py with the builtin server - works fine. > Afterward I went to another computer, which runs Apache. > I want > https://contr1.mydomain.com to route to https://myapp.mydomain.com/contr1 > https://contr2.mydomain.com to route to https://myapp.mydomain.com/contr2 > https://contr3.mydomain.com to route to https://myapp.mydomain.com/contr3 > > But it seems, that Apache wants three virtual servers > (https://contr1.mydomain.com and so on). > Is it possible to solve this problem with one virtual server and the > routes.py-file?
I'm no expert on Apache configuration, but I think you want to have a single VirtualHost section with something like this: ServerName contr1.mydomain.com ServerAlias contr2.mydomain.com ServerAlias contr3.mydomain.com http://httpd.apache.org/docs/current/vhosts/examples.html -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
