Re: [us...@httpd] Help needed to set correct permissions

2010-02-04 Thread Perl Whore
l make files executable if and only if at least one executable bit > was already set in the file's permissions. > > --Pete > -Original Message- > From: Philip Wigg [mailto:p...@philipwigg.co.uk] > Sent: Thursday, February 04, 2010 9:48 AM > To: users@httpd.apache.or

Re: [us...@httpd] Help needed to set correct permissions

2010-02-04 Thread Perl Whore
I'm still getting the permission error. [Thu Feb 04 06:47:11 2010] [error] [client 1.2.3.4] (13)Permission denied: access to / denied [Thu Feb 04 07:29:05 2010] [error] [client 1.2.3.4] (13)Permission denied: access to /test.htm denied [Thu Feb 04 07:29:08 2010] [error] [client 1.2.3.4] (13)Permis

Re: [us...@httpd] Help needed to set correct permissions

2010-02-04 Thread Perl Whore
Thanks, mod_userdir looks interesting. I'll use that. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr..

Re: [us...@httpd] Help needed to set correct permissions

2010-02-04 Thread Perl Whore
ardt wrote: > > -- > From: "Perl Whore" > Sent: 04 February, 2010 12:38 > To: > Subject: [us...@httpd] Help needed to set correct permissions > >> I'm running a default httpd install from the yum repository (Fedora >> 12). The user and g

Re: [us...@httpd] Help needed to set correct permissions

2010-02-04 Thread Perl Whore
drwx-- 4 somebody apache 4096 2010-02-03 12:34 somebody On 02/04/2010 07:04 PM, Daniel Reinhardt wrote: > > -- > From: "Perl Whore" > Sent: 04 February, 2010 12:38 > To: > Subject: [us...@httpd] Help neede

[us...@httpd] Help needed to set correct permissions

2010-02-04 Thread Perl Whore
I'm running a default httpd install from the yum repository (Fedora 12). The user and group that starts the httpd process is "apache" (default configuration in httpd.conf). The default page is located in /var/www/html/ I have a few users on this box for whom I need to setup virtual hosts and thei

Re: [us...@httpd] mod_proxy auth from PHP?

2009-12-20 Thread Perl Whore
Ah, thanks. This is a good idea. I didn't know about mod_auth_memcookie. Yes, it'll be great if you share your configuration so I can have a better understanding. On Mon, Dec 21, 2009 at 6:21 AM, Devraj Mukherjee wrote: > On Mon, Dec 14, 2009 at 11:04 PM, Perl Whore wrote: &

Re: [us...@httpd] Allowing users access to their websites (Possibly OT?)

2009-12-19 Thread Perl Whore
How about sftp without access to the shell? It's secure and most ftp clients support the protocol. On Sat, Dec 19, 2009 at 9:50 PM, LuKreme wrote: > I have several users who have websites on my Apache 2.2.13/FreeBSD > 8.0-RELEASE server and I give them access to their files via webdav. This > m

Re: [us...@httpd] What is wrong with this RewriteCond?

2009-12-18 Thread Perl Whore
I got it to work after going through the logs. The next thing I need to do is make it override the Server header of the internal server. Can that be done with mod_proxy? - The official User-To-User support forum of the Apache HTT

Re: [us...@httpd] What is wrong with this RewriteCond?

2009-12-18 Thread Perl Whore
rily the rest of the conditions that are set. > > Can you add the code pls as the next part seems a little unclear. > > > -Original Message- > From: Perl Whore [mailto:whorep...@gmail.com] > Sent: 18 December 2009 10:35 > To: users@httpd.apache.org > Subject

Re: [us...@httpd] What is wrong with this RewriteCond?

2009-12-18 Thread Perl Whore
I read the docs for the flags and it says for [C] that if a rule is not matched then it skips the rest of the rules. What I'm trying to do are set individual rules for the same condition and not a chain of rules. So only the rule that match should be applied. -

Re: [us...@httpd] What is wrong with this RewriteCond?

2009-12-17 Thread Perl Whore
I gave this a try: RewriteEngine On RewriteCond %{HTTP_COOKIE} !^.*test=test.*$ RewriteRule /inbox$ /index.php RewriteCond %{HTTP_COOKIE} !^.*test=test.*$ RewriteRule /compose-mail$ /index.php RewriteCond %{HTTP_COOKIE} ^.*test=test.*$ RewriteRule /inbox$ http://127.0.0.1:22131/ [P] RewriteCond

Re: [us...@httpd] What is wrong with this RewriteCond?

2009-12-17 Thread Perl Whore
>> Envoyé : jeudi 17 décembre 2009 22:38 >> À : users@httpd.apache.org >> Objet : Re: [us...@httpd] What is wrong with this RewriteCond? >> >> On Thu, Dec 17, 2009 at 4:24 PM, Perl Whore wrote: >> > RewriteEngine On >> > RewriteCond %{HTTP_COOKIE} !t

[us...@httpd] What is wrong with this RewriteCond?

2009-12-17 Thread Perl Whore
RewriteEngine On RewriteCond %{HTTP_COOKIE} !test RewriteRule /inbox$ /index.php RewriteRule /compose-mail$ /index.php <--- this works RewriteCond %{HTTP_COOKIE} test RewriteRule /compose-mail$ /proxy/ <--- this does not. RewriteRule /inbox$ http://127.0.0.1:22131/ [P] RewriteRule /inbox/(.+) ht

[us...@httpd] Is it possible to disable the Server header from mod_proxy destination?

2009-12-17 Thread Perl Whore
I'm using the [P] flag with mod_rewrite to forward requests to an internal application server but the Server header returned is that of the application server's and not Apache's. Is this the normal behaviour? If it is, can I make Apache override that with the Apache version instead? --

[us...@httpd] mod_proxy auth from PHP?

2009-12-14 Thread Perl Whore
Here is the situation: I have a php login page at https://login.mydomain.com and an internal server listening only on localhost http://localhost:12345 I want mod_proxy to send to the internal server only if auth was successful from the php login page. The user/pass can be in the .php file itself