Re: [us...@httpd] Windows Apache installer question

2010-12-24 Thread William A. Rowe Jr.
On 12/24/2010 10:28 AM, Igor Galić wrote: > > - "William A. Rowe Jr." wrote: > >> On 12/22/2010 2:01 PM, Jorge Canha wrote: >>> I'm currently using: >>> >>> msiexec /i httpd.msi /passive ALLUSERS=1 serveradmin=ad...@localhost >> SERVERNAME=localhost >>> SERVERDOMAIN=localhost SERVERPORT=80 >

Re: [us...@httpd] Restricting config to a single virtualhost

2010-12-24 Thread Lorenzo Milesi
> And what's wrong with having the config (included) in the SSL-only > vhost alone? Because I would need to place those config files elsewhere, which means every time I upgrade the package I should take care of remembering where they are and update them. This way they're in place, and aptitude w

Re: [us...@httpd] Windows Apache installer question

2010-12-24 Thread Igor Galić
- "William A. Rowe Jr." wrote: > On 12/22/2010 2:01 PM, Jorge Canha wrote: > > I'm currently using: > > > > msiexec /i httpd.msi /passive ALLUSERS=1 serveradmin=ad...@localhost > SERVERNAME=localhost > > SERVERDOMAIN=localhost SERVERPORT=80 > INSTALLDIR=%SYSTEMDRIVE%\apache > > > > To inst

Re: [us...@httpd] Restricting config to a single virtualhost

2010-12-24 Thread Igor Galić
- "Lorenzo Milesi" wrote: > > Another solution: Add SSLRequireSSL to the gitweb.conf file. All > > vhosts will > > see the gitweb configuration, but only the SSL host will allow > access. > > I like this solution the most. > This gives Forbidden to all the hosts, meaning that I cannot use t

Re: [us...@httpd] Restricting config to a single virtualhost

2010-12-24 Thread Lorenzo Milesi
> Another solution: Add SSLRequireSSL to the gitweb.conf file. All > vhosts will > see the gitweb configuration, but only the SSL host will allow access. I like this solution the most. This gives Forbidden to all the hosts, meaning that I cannot use the same dir on other vhosts, right? Not a big

Re: [us...@httpd] Restricting config to a single virtualhost

2010-12-24 Thread Joost de Heer
Move the file from conf.d to another location, and Include the file in your ssl host. Another solution: Add SSLRequireSSL to the gitweb.conf file. All vhosts will see the gitweb configuration, but only the SSL host will allow access. Joost

Re: [us...@httpd] Restricting config to a single virtualhost

2010-12-24 Thread Joost de Heer
Debian includes conf.d/* before sites-enabled/*, this means gitweb is loaded before default-ssl. Reverting this behavior is not a big deal, but how do I make gitweb available only to the SSL website? I know I could place gitweb content into default-ssl, but I'd rather keep them separated, if possi

[us...@httpd] Restricting config to a single virtualhost

2010-12-24 Thread Lorenzo Milesi
Hi. I'm using Apache2 on Ubuntu Server. I've configured three virtual hosts, two on port 80 and one on port 443. I've also several web apps, some directly placed in /var/www, some others installed system wide, which are configured by files placed in conf.d/. Here comes my problem, because this ma