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 before

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 38

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 FollowS

[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 t

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 Requ

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 Site

[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 pag

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 "C:

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 wrote: > > I have installed wampserver

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 and I > also get the s

[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" #

[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 /dev/n

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 add

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

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 [L] 'A web-pa

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

On Tue, Nov 13, 2012 at 4:54 PM, Lester Caine 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' is not us

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

On Wed, Nov 14, 2012 at 8:54 AM, 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 ad

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 quest

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 per

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 relat

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. But

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

On Wed, Nov 14, 2012 at 8:19 AM, Lester Caine 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 is makin

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 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 ...

On 14/11/2012 7:44 AM, "Jeroen Geilman" 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 cleared but

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. mod_info

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 flippi

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 /wiki/index.php?page=Life+in+

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 cor

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 whe

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 http://evesham.uk.com/wiki/Life+in+Evesha

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

On Tue, Nov 13, 2012 at 11:16 AM, Kevin A. McGrail wrote: > 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 ...

On Tue, Nov 13, 2012 at 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 wh

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 recei

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

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 receiving "client denied by server configuration"

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 f

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 >> http://evesha

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 http://evesh

[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 http://eveshamtc.lsces.co.uk/wik

[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).