Re: [users@httpd] 403 issues on Ubuntu

Thanks! Turned out that I didn't have some options set and it was trying to rewrite! On Sun, Aug 15, 2021 at 5:24 PM Eric Covener wrote: > The error_log probably has a hint. Likely missing world read/execute > on /home/kygekteam > > On Sun, Aug 15, 2021 at 6:22 PM David Jentes > wrote: > > > >

Re: [users@httpd] 403 issues on Ubuntu

The error_log probably has a hint. Likely missing world read/execute on /home/kygekteam On Sun, Aug 15, 2021 at 6:22 PM David Jentes wrote: > > I'm part of the programming group KygekTeam, and I host and co-manage an > Ubuntu VM. The co-manager and leader of KygekTeam insists that the website

[users@httpd] 403 issues on Ubuntu

I'm part of the programming group KygekTeam, and I host and co-manage an Ubuntu VM. The co-manager and leader of KygekTeam insists that the website is in the home directory of the shared user we use. We have done this once before with our website for our testing Minecraft server's website, as we

Re: [users@httpd] 403 Forbidden on symbolic links - totally won't do it.

namei -mo /var/www/sellfam.com/public/minecraft/www will help you here. Check each path. On Sun, 2 Jun 2019 at 05:47, timothylegg . wrote: > These are access.log and error.log entries. > > I added the + to the FollowSymLinks and no obvious change occurred, > These resemble the same errors

Re: [users@httpd] 403 Forbidden on symbolic links - totally won't do it.

These are access.log and error.log entries. I added the + to the FollowSymLinks and no obvious change occurred, These resemble the same errors before modifying the file. I remembered to restart apache2. 87.138.223.233 - - [02/Jun/2019:11:35:08 +0200] "GET /minecraft/www/index.php HTTP/1.1" 403

Re: [users@httpd] 403 Forbidden on symbolic links - totally won't do it.

> I get a 403 Forbidden error at https://sellfam.com/minecraft/www/ > > I told it to follow symlinks in the sites-available files and it > should just work, but doesn't... What on earth is wrong? Oh yes, I > did remember to restart apache2 as well. What does the error log say? > Options

[users@httpd] 403 Forbidden on symbolic links - totally won't do it.

I have spent the past two hours trying to find the magic needed to get my external drive symlink to be part of a friend's website. I've never been able to do this in the past and have simply reinstalled linux on larger and larger volumes as a solution to running out of free space, but I'm simply

Re: [users@httpd] 403 Forbidden Error on Apache 2.4

Directory / is the root of the filesystem, so it should always be set in server config with Require all denied, it is not the documentroot, chances are you have a Directory directive elsewhere denying, also make 100% sure you don't mix Order/Allow/Deny with 2.4 directives. So: Server config

Re: [users@httpd] 403 Forbidden Error on Apache 2.4

I think it’s the L in your rewrite rule. It stands for Last and means it won’t process any further rules. Remove it and it should (maybe) work. Someone else feel free to correct me if I’m wrong. > On Feb 5, 2019, at 8:55 PM, Jayaram Ponnusamy > wrote: > > Dear All, > Our Site is Public

[users@httpd] 403 Forbidden Error on Apache 2.4

Dear All, Our Site is Public Site and there is no restriction @ any level. We are using apache on top of Java based CMS (Tomcat Server). Recently we upgraded Apache from 2.2.21 to 2.4.25. Where ever Order allow,deny & Allow from all coming there we changed it to Require all granted but root

Re: [users@httpd] 403 error upon upgrade

Eureka!! I found a new or recently revised file: /etc/apache2/listen.conf. That had a pair of listen lines under NameVirtualHost that I commented out. Restarting apache then produced a running server. Thanks, guys, for your patience and help! I will keep your emails in my Whatthehell? folder

Re: [users@httpd] 403 error upon upgrade

vhosts do not bind to ports - the Listen directive does. On Thu, Oct 4, 2018 at 3:17 PM Filipe Cifali wrote: > Because something else could be listening on those ports, preventing httpd > from starting. This is not so uncommon to happen. httpd is complaining on > listening to both IPv4 and

Re: [users@httpd] 403 error upon upgrade

Because something else could be listening on those ports, preventing httpd from starting. This is not so uncommon to happen. httpd is complaining on listening to both IPv4 and IPv6, so maybe a greedy virtualhost is trying to map more addresses than it should? On Thu, Oct 4, 2018 at 3:59 PM Jack

Re: [users@httpd] 403 error upon upgrade

Of course, since Apache isn't running -- failed to start -- why would I get any LISTEN ports? > On 4 Oct 2018, at 11:46, Jack M. Nilles wrote: > > Here's what I get for the first part of that: > > # netstat -napo | egrep "(:80|:443)" > tcp0 0 1.2.3.4:43160 23.210.206.246:443

Re: [users@httpd] 403 error upon upgrade

Here's what I get for the first part of that: # netstat -napo | egrep "(:80|:443)" tcp0 0 1.2.3.4:43160 23.210.206.246:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0) tcp0 0 1.2.3.4:59116 107.14.47.80:80 TIME_WAIT - timewait

Re: [users@httpd] 403 error upon upgrade

On Thu, Oct 4, 2018 at 2:01 PM Jack M. Nilles wrote: > > Here's what I get: > > # lsof -i:443 > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > java 710 root 245u IPv6 49204 0t0 TCP > server.site1.com:52752->central.crashplanpro.com:https (ESTABLISHED) > squid 1961

Re: [users@httpd] 403 error upon upgrade

Jack, don't confuse INCOMING/OUTGOING connections with LISTEN. Seems this site is gathering some info from other sites, you can see the commands running *Java* and *squid*, if you have netstat installed (otherwise just install it because it's super flexible and easy to use?) run a `netstat

Re: [users@httpd] 403 error upon upgrade

Here's what I get: # lsof -i:443 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java 710 root 245u IPv6 49204 0t0 TCP server.site1.com:52752->central.crashplanpro.com:https (ESTABLISHED) squid 1961 squid 13u IPv4 19134 0t0 TCP server.site1.com

Re: [users@httpd] 403 error upon upgrade

http://wiki.apache.org/httpd/CouldNotBindToAddress will help you troubleshoot that error. On Wed, Oct 3, 2018 at 8:21 PM Filipe Cifali wrote: > Jack, the logs saying you can't bind the addresses: > > Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use: > AH00072: make_sock:

Re: [users@httpd] 403 error upon upgrade

Jack, the logs saying you can't bind the addresses: Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443 Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use: AH00072: make_sock: could not bind to address

Re: [users@httpd] 403 error upon upgrade

A few minutes later I get: apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled) Active: failed (Result: exit-code) since Wed 2018-10-03 15:10:27 PDT; 38s ago Process: 5147 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k

Re: [users@httpd] 403 error upon upgrade

Well, I have now set SuSE's YaST to reconfigure apache2 using the same vhosts.conf file while ensuring that php5 is running. Now apache won't start. I have moved from a 403 error to a site can't be reached error. I get the following output from systemctl status apache2.service: apache2.service

Re: [users@httpd] 403 error upon upgrade

The main document root does not interfere with your vhosts. See: http://httpd.apache.org/docs/current/vhosts/name-based.html#using (See note about "Main host goes away") On Wed, Oct 3, 2018 at 2:40 PM Jack M. Nilles wrote: > I just noticed, upon running 'apache2ctl -S', that the server root is

Re: [users@httpd] 403 error upon upgrade

I just noticed, upon running 'apache2ctl -S', that the server root is listed as "/srv/www" and the document root as "/srv/www/htdocs" while the actual document roots are elsewhere (such as /home/data/site1/htdocs). I'm assuming that the vhosts.conf file takes care of this linkage. If it doesn't

Re: [users@httpd] 403 error upon upgrade

Jack, you have to either load mod_php (which comes from compiling / installing PHP in a certain way) or change the way you are using PHP on the overall with httpd. Searching for how to install mod_php on SUSE X (being X the version you are running) should provide frutiferous info, but I'm a

Re: [users@httpd] 403 error upon upgrade

Frank, My main concern is to get apache to run with php at all, never mind scalability issues. So far everything looks fine except that it doesn't work. Maybe somewhere in the bowels of SuSE 42.1 there is an error. Jack - To

Re: [users@httpd] 403 error upon upgrade

Jack, The point is not to use non-threaded to increase your performance and scalability. The event mpm has the ability to run many threads per process, which in turn can drastically increase the number of simultaneous clients you can serve. On Tue, Oct 2, 2018 at 4:34 PM Jack M. Nilles wrote:

Re: [users@httpd] 403 error upon upgrade

mpm_prefork_module is/was loaded. > On 2 Oct 2018, at 8:24, Frank Gingras wrote: > > http://wiki.apache.org/httpd/php is a good > starting point - I would recommend not using mod_php, unless you have a good > reason to use it. > > Nowadays, mod_proxy_fcgi

Re: [users@httpd] 403 error upon upgrade

The package manager (YaST) shows php5.5 as installed so it should have php-fpm in its code base. I notice that /etc/php5/apache2/php.ini at present has short_open_tag = Off which might be the clue to its ignoring all the code in these sites that use -- or not. The commented text is a tad

Re: [users@httpd] 403 error upon upgrade

Also double check what version of PHP SUSE server pkg manager is providing now, this seems like a change of version where the pkg manager gone rogue (maybe missing dependency on tree?) On Tue, Oct 2, 2018 at 12:24 PM Frank Gingras wrote: > http://wiki.apache.org/httpd/php is a good starting

Re: [users@httpd] 403 error upon upgrade

http://wiki.apache.org/httpd/php is a good starting point - I would recommend not using mod_php, unless you have a good reason to use it. Nowadays, mod_proxy_fcgi and php-fpm is trivial to set up, and allow you to use a threaded mpm, such as event. On Tue, Oct 2, 2018 at 11:21 AM Jack M. Nilles

Re: [users@httpd] 403 error upon upgrade

Sure enough, there seems to be no php module loaded: Loaded Modules: core_module (static) so_module (static) http_module (static) mpm_prefork_module (static) unixd_module (static) systemd_module (static) actions_module (shared) alias_module (shared) auth_basic_module (shared)

Re: [users@httpd] 403 error upon upgrade

It is indeed recommended *not* to use for that very reason. If the module isn't loaded, then those directives will not be evaluated. Run apachectl -M to see loaded modules. On Mon, Oct 1, 2018 at 5:27 PM Filipe Cifali wrote: > Are you sure you have mod_php installed and active? This would

Re: [users@httpd] 403 error upon upgrade

Are you sure you have mod_php installed and active? This would explain the failing DirIndex and all of this sudden change On Mon, 1 Oct 2018 at 17:36 Jack M. Nilles wrote: > /etc/apache2/conf.d/php5.conf is as follows: > > > >SetHandler application/x-httpd-php > >

Re: [users@httpd] 403 error upon upgrade

/etc/apache2/conf.d/php5.conf is as follows: SetHandler application/x-httpd-php SetHandler application/x-httpd-php-source DirectoryIndex index.php4 DirectoryIndex index.php5 DirectoryIndex index.php Why this doesn't

Re: [users@httpd] 403 error upon upgrade

It worked before because you had other DirectoryIndex directives (mostly unaware of that fact). Now, you need DIrectoryIndex index.html index.php or just DirectoryIndex index.php On Sun, Sep 30, 2018 at 4:36 PM Jack M. Nilles wrote: > I don't have an index.html in that directory -- only

Re: [users@httpd] 403 error upon upgrade

I don't have an index.html in that directory -- only index.php. I suppose I could put in an html file that immediately switches to the php page. That site has always worked before with no index.html file. Why not now? - To

Re: [users@httpd] 403 error upon upgrade

Jerry Martinez > Owner & Lead Developer > > JM Web Services, Inc > 786.412.1660 | www.jmweb.net > > > -Original Message- > From: Jerry Martinez [mailto:je...@jmweb.net] > Sent: Sunday, September 30, 2018 2:47 PM > To: 'users@httpd.apache.org' > Subject: R

RE: [users@httpd] 403 error upon upgrade

worked flawlessly. Jerry Martinez Owner & Lead Developer JM Web Services, Inc 786.412.1660 | www.jmweb.net -Original Message- From: Jerry Martinez [mailto:je...@jmweb.net] Sent: Sunday, September 30, 2018 2:47 PM To: 'users@httpd.apache.org' Subject: RE: [users@httpd] 403 error upon upg

RE: [users@httpd] 403 error upon upgrade

:14 PM To: users@httpd.apache.org Subject: Re: [users@httpd] 403 error upon upgrade > Date: Sunday, September 30, 2018 10:44:28 -0700 > From: "Jack M. Nilles" > > Basically the same as before: > > [Sun Sep 30 10:29:05.708882 2018] [autoindex:error] [pid 3663] [cl

Re: [users@httpd] 403 error upon upgrade

> Date: Sunday, September 30, 2018 10:44:28 -0700 > From: "Jack M. Nilles" > > Basically the same as before: > > [Sun Sep 30 10:29:05.708882 2018] [autoindex:error] [pid 3663] > [client 220.181.51.119:50416] AH01276: Cannot serve directory > /home/data/site1/htdocs/: No matching

Re: [users@httpd] 403 error upon upgrade

Basically the same as before: [Sun Sep 30 10:29:05.708882 2018] [autoindex:error] [pid 3663] [client 220.181.51.119:50416] AH01276: Cannot serve directory /home/data/site1/htdocs/: No matching DirectoryIndex (index.html,index.html.var) found, and server-generated directory index forbidden by

Re: [users@httpd] 403 error upon upgrade

What does the error log say now? On Sat, Sep 29, 2018 at 5:01 PM Jack M. Nilles wrote: > I have found another DirectoryIndex directive in > /etc/apache2/conf.d/gitweb.conf. Since this is higher up the chain than the > vhosts.d directory that might be what's producing the file download >

Re: [users@httpd] 403 error upon upgrade

I have found another DirectoryIndex directive in /etc/apache2/conf.d/gitweb.conf. Since this is higher up the chain than the vhosts.d directory that might be what's producing the file download behavior. If I omit the DirectoryIndex line and restart apache then I at least just get the 403 error

Re: [users@httpd] 403 error upon upgrade

You still need to set AllowOverride none in the block to prevent .htaccess files from interfering. As for the index file being downloaded, if it's static content, see: http://httpd.apache.org/docs/current/mod/mod_mime.html#addtype If it's a php file, see: http://wiki.apache.org/httpd/php

Re: [users@httpd] 403 error upon upgrade

Frank, Sorry for the typos. I've corrected the code below to be consistent. The error message was, and is (I am anonymizing the directory details): [Fri Sep 28 15:15:39.301689 2018] [autoindex:error] [pid 17591] [client 1.2.3.4:45731] AH01276: Cannot serve directory /home/data/site1/htdocs/:

Re: [users@httpd] 403 error upon upgrade

There is no reference to "webdir" anywhere in your configuration, so you effectively munged it to the point that we cannot help you. Further, I would recommend setting AllowOverride none in every single block - the last thing you want is for a rogue .htaccess file to interfere. If the sole

[users@httpd] 403 error upon upgrade

Two days ago I upgraded my SUSE server. It serves three websites as virtual sites. All of the sites run php. Upon restarting apache 2.4 I got the following error message: [Wed Sep 26 07:36:55.666104 2018] [autoindex:error] [pid 12345] [client 1.2.3.4:50430] AH01276: Cannot serve directory

Re: [users@httpd] 403 Forbidden for git repository over http

No Response. Please let me know if any more inputs are required. Regards, Amit From: Amit Agrawal88/India/IBM@IBMIN To: users@httpd.apache.org Date: 08/22/2016 05:55 PM Subject:[users@httpd] 403 Forbidden for git repository over http Hi All, I am trying to setup a central

[users@httpd] 403 Forbidden for git repository over http

Hi All, I am trying to setup a central Git server which can be accessed over HTTP protocol. I have installed Bitnami WAMP stack with Apache 2.4 version. The Git repository is located in C:\Git\Repos. In httpd.conf file, I have changed the Document Root folder to C:\Git\Repos DocumentRoot

Re: [users@httpd] 403 Forbidden

Dear Eric, First of all，thank you for attention to my issuse :) Yes,I have updated httpd.conf file as Administrator and I uploaded the error log and the httpd.conf file 2016-07-06 18:35 GMT+08:00 Eric Covener : > On Wed, Jul 6, 2016 at 4:13 AM, newlifeR REN

Re: [users@httpd] 403 Forbidden

On Wed, Jul 6, 2016 at 4:13 AM, newlifeR REN wrote: > I have installed wampserver(apache 2.4.18) on windows when i access the > server on other pc and I have got en Error 403(you didn't have permission to > access on this server).I have changed the httpd.conf file following

[users@httpd] 403 Forbidden

Hi bros, I have installed wampserver(apache 2.4.18) on windows when i access the server on other pc and I have got en Error 403(you didn't have permission to access on this server).I have changed the httpd.conf file following and I also get the same error 403: DocumentRoot "c:/wamp/www" #

Re: [users@httpd] 403 and I don't understand why

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/13/2015 04:06 PM, Richard wrote: Your apache access control directives are from pre-2.4, and likely causing your problems now that your apache is 2.4.x. See: http://httpd.apache.org/docs/2.4/upgrading.html Thank you. That provided the

[users@httpd] 403 and I don't understand why

httpd v2.4.10 linux v3.16.7-21-desktop x86_64 Access to this site used to work oh-so-long ago. I have had no need to access the (local) site for many months (at least). The Apache server has been updated regularly since then. The directories and files are not read-protected (See below).

Re: [users@httpd] 403 and I don't understand why

Original Message Date: Monday, July 13, 2015 03:52:24 PM -0700 From: James Moe ji...@sohnen-moe.com httpd v2.4.10 linux v3.16.7-21-desktop x86_64 Access to this site used to work oh-so-long ago. I have had no need to access the (local) site for many months

[users@httpd] 403 Forbidden on unicode urlencoded GET parameters (SecFilter issue)

Hi, I get some weird 403 errors while trying to use unicode urlencoded GET parameters. With ascii characters it works: user@system:~$ curl -s -o /dev/null -I -w '%{http_code}' ' http://domain/script.php?action=Mettre+a+jour' 302 With unicode characters it works: user@system:~$ curl -s -o

Re: [users@httpd] 403 Forbidden ...

Lester Caine wrote: I'm missing something simple I am sure ... Am moving from 2.2 to 2.4 and this works on 2.2! http://eveshamtc.lsces.co.uk works ... The vhost file has 301 redirects from the original .aspx links, so http://eveshamtc.lsces.co.uk/lifeinevesham.aspx is redirected to

Re: [users@httpd] 403 Forbidden ...

On 11/13/2012 3:45 AM, Lester Caine wrote: Lester Caine wrote: I'm missing something simple I am sure ... Am moving from 2.2 to 2.4 and this works on 2.2! http://eveshamtc.lsces.co.uk works ... The vhost file has 301 redirects from the original .aspx links, so

Re: [users@httpd] 403 Forbidden ...

May be as a first step, start enabling Rewrite log. Put RewriteLogLevel at 5, to see what is being rewrited. Then based on that we can check what it's making it fail. best, On 11/13/2012 09:45 AM, Lester Caine wrote: Lester Caine wrote: I'm missing something simple I am sure ... Am moving

Re: [users@httpd] 403 Forbidden ...

On 11/13/2012 11:12 AM, Lester Caine wrote: Ben Johnson wrote: You, good sir, would be well-served to install mod_info, which will tell you exactly which directives are being applied to which containers. We can guess at this all day, but there are a number of reasons for which you might be

Re: [users@httpd] 403 Forbidden ...

On Tue, Nov 13, 2012 at 11:12 AM, Lester Caine les...@lsces.co.uk wrote: Ben Johnson wrote: You, good sir, would be well-served to install mod_info, which will tell you exactly which directives are being applied to which containers. We can guess at this all day, but there are a number of

Re: [users@httpd] 403 Forbidden ...

On Tue, Nov 13, 2012 at 11:16 AM, Kevin A. McGrail kmcgr...@pccc.comwrote: This might be helpful in determining the error: LINK REMOVED P.S. OK it's not helpful at all but I couldn't resist posting it. The cuteness overwhelmed me. Next time, resist.

Re: [users@httpd] 403 Forbidden ...

Antonio Vidal Ferrer wrote: May be as a first step, start enabling Rewrite log. Put RewriteLogLevel at 5, to see what is being rewrited. Then based on that we can check what it's making it fail. The rewrite is apparently doing the correct conversion from

Re: [users@httpd] 403 Forbidden ...

I am going to guess that there is a conflict between your rewrite rules and actual directory names. I am guessing that the 403 is generated by directory index not being allowed. When I go to http://evesham.uk.com/wiki/index.php?page=Life+in+Evesham, the page actually shows up (and it also does

Re: [users@httpd] 403 Forbidden ...

On 11/13/2012 11:45 AM, Lester Caine wrote: Antonio Vidal Ferrer wrote: May be as a first step, start enabling Rewrite log. Put RewriteLogLevel at 5, to see what is being rewrited. Then based on that we can check what it's making it fail. The rewrite is apparently doing the correct

Re: [users@httpd] 403 Forbidden ...

Ben Johnson wrote: I'm not convinced that mod_rewrite has anything to do with this; it can probably be removed from the equation entirely. I mean, I assume that you receive the same error (client denied by server configuration: /wiki/index.php) when you hit the URL

Re: [users@httpd] 403 Forbidden ...

Lester Caine wrote: Found a few little niggles while sorting mod_info. I was still running mod_access_compat and switching that off flagged a couple of problems. All have now been cleared but no change to the 403 error on rewrite results. mod_info is now loaded, but currently I'm just

Re: [users@httpd] 403 Forbidden ...

On 11/13/2012 09:34 PM, Lester Caine wrote: Lester Caine wrote: Found a few little niggles while sorting mod_info. I was still running mod_access_compat and switching that off flagged a couple of problems. All have now been cleared but no change to the 403 error on rewrite results.

Re: [users@httpd] 403 Forbidden ...

On 14/11/2012 7:44 AM, Jeroen Geilman jer...@adaptr.nl wrote: On 11/13/2012 09:34 PM, Lester Caine wrote: Lester Caine wrote: Found a few little niggles while sorting mod_info. I was still running mod_access_compat and switching that off flagged a couple of problems. All have now been

Re: [users@httpd] 403 Forbidden ...

On 11/13/2012 3:34 PM, Lester Caine wrote: Lester Caine wrote: Found a few little niggles while sorting mod_info. I was still running mod_access_compat and switching that off flagged a couple of problems. All have now been cleared but no change to the 403 error on rewrite results.

Re: [users@httpd] 403 Forbidden ...

Ben Johnson wrote: Most likely, the root of the problem is in how that /wiki location is defined. Did you define that location yourself? Or did you just install some off-the-shelf Wikimedia package for your OS? This is making sense Ben - Thanks for the pointers This is one of many 'bitweaver'

Re: [users@httpd] 403 Forbidden ...

On Wed, Nov 14, 2012 at 8:19 AM, Lester Caine les...@lsces.co.uk wrote: Ben Johnson wrote: Most likely, the root of the problem is in how that /wiki location is defined. Did you define that location yourself? Or did you just install some off-the-shelf Wikimedia package for your OS? This

Re: [users@httpd] 403 Forbidden ...

Ben Johnson wrote: Still, I'm not sure that this has anything to do with URL-rewriting. This seems related to path resolution in the PHP application (which mod_rewrite may influence, to be fair). This is why any developer that uses relative file paths in this way should be scorned, publicly.

Re: [users@httpd] 403 Forbidden ...

On 11/13/2012 4:37 PM, Lester Caine wrote: Ben Johnson wrote: Still, I'm not sure that this has anything to do with URL-rewriting. This seems related to path resolution in the PHP application (which mod_rewrite may influence, to be fair). This is why any developer that uses relative file

Re: [users@httpd] 403 Forbidden ...

Igor Cicimov wrote: So this is a different machine??? If you haven't set the wiki file permissions properly on the new server the access will not work no matter which version of apache you are using. Again, is there any wiki apache config file for the wiki directory? To start with compare the

Re: [users@httpd] 403 Forbidden ...

Ben Johnson wrote: My rewrite rules are stored in a config file 'mod_rewrite.conf' which is loaded in every vhost.d config file. To get this working I've copied all the code directly into one of the vhost.conf files and then added the hard coded paths to the re-write rules. So now the question

Re: [users@httpd] 403 Forbidden ...

On Wed, Nov 14, 2012 at 8:54 AM, Lester Caine les...@lsces.co.uk wrote: Ben Johnson wrote: My rewrite rules are stored in a config file 'mod_rewrite.conf' which is loaded in every vhost.d config file. To get this working I've copied all the code directly into one of the vhost.conf files and

Re: [users@httpd] 403 Forbidden ...

On Tue, Nov 13, 2012 at 4:54 PM, Lester Caine les...@lsces.co.uk wrote: lines like RewriteRule ^/?wiki/view/(.+)$ /wiki/index.php?page=$1 [L] have been ammended to RewriteRule ^/?wiki/view/(.+)$ /srv/website/eveshamtc.org.uk/**wiki/index.php?page=$1 [L] 'A web-path to a resource'

Re: [users@httpd] 403 Forbidden ...

Igor Cicimov wrote: lines like RewriteRule ^/?wiki/view/(.+)$ /wiki/index.php?page=$1 [L] have been ammended to RewriteRule ^/?wiki/view/(.+)$ /srv/website/eveshamtc.org.uk/__wiki/index.php?page=$1 http://eveshamtc.org.uk/wiki/index.php?page=$1 [L] 'A

Re: [users@httpd] 403 Forbidden ...

On 11/13/2012 4:54 PM, Lester Caine wrote: Ben Johnson wrote: My rewrite rules are stored in a config file 'mod_rewrite.conf' which is loaded in every vhost.d config file. To get this working I've copied all the code directly into one of the vhost.conf files and then added the hard coded

Re: [users@httpd] 403 Forbidden ...

Ben Johnson wrote: On 11/13/2012 4:54 PM, Lester Caine wrote: Ben Johnson wrote: My rewrite rules are stored in a config file 'mod_rewrite.conf' which is loaded in every vhost.d config file. To get this working I've copied all the code directly into one of the vhost.conf files and then

[users@httpd] 403 Forbidden ...

I'm missing something simple I am sure ... Am moving from 2.2 to 2.4 and this works on 2.2! http://eveshamtc.lsces.co.uk works ... The vhost file has 301 redirects from the original .aspx links, so http://eveshamtc.lsces.co.uk/lifeinevesham.aspx is redirected to

[users@httpd] 403 forbidden

Env: Windows/apache 2.2  httpd.conf:   Forward proxy configuration with Basic auth. Why would httpd respond with 403 for a valid http request? There are no special restrictions configured besides basic Proxy setup on top of standard httpd.conf (after clean install).

Re: [users@httpd] 403 error on Default Directory

dick gregor. PE J. Stephens onlineworkm...@gmail.com wrote: I know I should add the root directory due to security, but I am getting this error. website error.log: Thu Mar 24 19:23:05 2011] [error] [client 98.226.168.246] client denied by server configuration: / I guess I need to be

Re: [users@httpd] 403 error on Default Directory

dick gregor. PE Yehuda Katz yeh...@ymkatz.net wrote: On Thu, Apr 28, 2011 at 1:53 PM, J. Stephens onlineworkm...@gmail.commailto:onlineworkm...@gmail.com wrote: error log says [Thu Apr 28 13:50:57 2011] [error] [client 98.226.168.246] client denied by server configuration: / my website is

Re: [users@httpd] 403 error on Default Directory

dick gregor. PE J. Stephens onlineworkm...@gmail.com wrote: error log says [Thu Apr 28 13:50:57 2011] [error] [client 98.226.168.246] client denied by server configuration: / my website is at /var/www/testing600.remcycle.net/. Should it be saying that directory and not the root

Re: [users@httpd] 403 error on Default Directory

dick gregor. PE Yehuda Katz yeh...@ymkatz.net wrote: On Fri, Apr 29, 2011 at 11:00 AM, J. Stephens onlineworkm...@gmail.commailto:onlineworkm...@gmail.com wrote: The solution to the problem was that I needed to add a Directory/ to the vhost. I do not know why it would need the root

Re: [users@httpd] 403 error on Default Directory

I know I should add the root directory due to security, but I am getting this error. website error.log: Thu Mar 24 19:23:05 2011] [error] [client 98.226.168.246] client denied by server configuration: / I guess I need to be asking why it needs access to the root of the computer and not just

Re: [users@httpd] 403 error on Default Directory

On Sun, May 1, 2011 at 5:13 PM, J. Stephens onlineworkm...@gmail.com wrote: I know I should add the root directory due to security, but I am getting this error. website error.log: Thu Mar 24 19:23:05 2011] [error] [client 98.226.168.246] client denied by server configuration: / I guess I

Re: [users@httpd] 403 error on Default Directory

I think I found the real issue. In the vhosts it has RewriteEngine on RewriteCond %{HTTP_HOST} ^test.remcycle.net [NC] RewriteRule ^/(.*)$ /$1 RewriteCond %{HTTP_HOST} ^www.test.remcycle.net [NC] RewriteRule ^/(.*)$ /$1 After removing this and restarting the

Re: [users@httpd] 403 error on Default Directory

Use the PT flag if you rewrite in vhost context and the substitution is a url instead of a filesystem path. Url2file is the default, but when the substance prefix doesn't exist it treats it as url2url. PT forces it On May 1, 2011 9:52 PM, J. Stephens onlineworkm...@gmail.com wrote: I think I

Re: [users@httpd] 403 error on Default Directory

The solution to the problem was that I needed to add a Directory/ to the vhost. I do not know why it would need the root directory, but as long as it is fixed then I do not care. Would this cause any security risks or is it fine to add this directory? BTW: Thank you for your responses it has

Re: [users@httpd] 403 error on Default Directory

On Fri, Apr 29, 2011 at 11:00 AM, J. Stephens onlineworkm...@gmail.comwrote: The solution to the problem was that I needed to add a Directory/ to the vhost. I do not know why it would need the root directory, but as long as it is fixed then I do not care. Would this cause any security risks

[users@httpd] 403 error on Default Directory

I am getting 403 errors when I add a new vhost. at testing601.remcycle.net I get 403, but at testing601.remcycle.net/index.html it works. What are the possible causes of this 403 error? This server is running under Debian Squeeze Troubleshoot already done: 1.The directory is chmoded at 710

Re: [users@httpd] 403 error on Default Directory

On Thu, Apr 28, 2011 at 10:37 AM, J. Stephens onlineworkm...@gmail.comwrote: I am getting 403 errors when I add a new vhost. at testing601.remcycle.netI get 403, but at testing601.remcycle.net/index.html it works. What are the possible causes of this 403 error? Check the error log.

Re: [users@httpd] 403 error on Default Directory

error log says [Thu Apr 28 13:50:57 2011] [error] [client 98.226.168.246] client denied by server configuration: / my website is at /var/www/testing600.remcycle.net/. Should it be saying that directory and not the root directory? On Apr 28, 2011, at 10:40 AM, Yehuda Katz wrote: On Thu, Apr

Re: [users@httpd] 403 error on Default Directory

On Thu, Apr 28, 2011 at 1:53 PM, J. Stephens onlineworkm...@gmail.comwrote: error log says [Thu Apr 28 13:50:57 2011] [error] [client 98.226.168.246] client denied by server configuration: / my website is at /var/www/testing600.remcycle.net/. Should it be saying that directory and not the

[users@httpd] 403/

- The official User-To-User support forum of the Apache HTTP Server Project. See URL:http://httpd.apache.org/userslist.html for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org from the digest:

[users@httpd] 403 on XP accessing an XML database document

Environment: Windows XP Office with SP2 And Windows 2000 Professional Both have Apache 2.0.54 installed. Tested earlier with 2.0.48 In Apache I use the LoadModule directive so that I get access to an XML database. And I use the Location directive to define the access used for the

  1   2   >