| arooni | ahh i see |
| megaspaz | so debian loads very little... redhat loads everything... yada yada yada |
| emilylove | alright..well..thanks! even though I don't know what fixed it lol. Everything is working fine now *shrug* |
| wad | I'm trying to add an SSL virtual host. I've added "Listen 443" and "NameVirtualHost *:443" and a <VirtualHost *:443> block, but I keep getting this: [warn] NameVirtualHost *:443 has no VirtualHosts Any ideas? |
| fajita | thinking is *hard*! |
| action | wad pokes fajita |
| wad | pokes fajita |
| fajita | Ow! Quit it, wad! |
| jpeg | wad: only one NameVirtualHost *:443 per config file is required. if you have two, that's your problem. |
| wad | hmm jpeg: Aren't all the config files kind of stuck together into one large one, though? |
| jpeg | yes. so you need only one NameVirtualHost *:443 directive. |
| maxo | hi |
| wad | Right, and I'm fairly certain I only have one. I do have 5 NameVirtualHost *:80 directives. |
| maxo | I've got a server running on apache on HTTP, but it's also running on HTTPS. With the standard non-ssl site, apache takes into account .htaccess files, which block access to certain directories for example. the SSL site on the other hand doesn't. Is there something like a .htaccess file I can use for the SSL server? um is what I'm typing appearing? |
| trelly | are you trying the 'i type therefore i exist' thing? |
| maxo | trelly: no sorry, it's just I was having trouble with my connection earlier |
| wad | I can't see anything that maxo is typing. |
| action | wad ducks |
| wad | ducks |
| action | fajita quacks+alias ducks='du -cks * |
| fajita | quacks+alias ducks='du -cks * |
| maxo | I'd really appreciate some help though. At the moment my web server is at risk - I think it's a security risk, because anyone can browse through directories that are usually restricted just by using HTTPS. Apache SSL is basically ignoring my .htaccess files and I don't know why. |
| trelly | remove the 'Options Indexes' from the httpd.conf |
| engaged | how do i configure perl/apache to include the path to the current perl script in the list of places to look when opening files using relative paths? anyone? |
| jpeg | engaged: modperl or cgi? |
| olinux | engaged it's the destination folders permissions that determine if the script can write to them not the script itself |
| engaged | cgi |
| fajita | cgi is /http://httpd.apache.org/docs/2.0/howto/cgi.html |
| engaged | k |
| jpeg | depending on what you're doing, either chdir, specify the full path to the file, or a path relative from the server root. |
| imMute | engaged: " use lib '.'; " not really though or use FindBin; use lib "$FindBin::Path"; |
| jpeg | that would work for @INC, but I'm not sure if that's what he's asking. |
| imMute | engaged: when opening relative files its always taken relative to the current working dir |
| engaged | k |
| jpeg | what kind of files are these, engaged? are you trying to use a lib? are you writing to a file? are you printing links to images? |