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

2019-06-02 Thread Frank Gingras
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 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 3852 "-" "Mozilla/5.0 (X11;
> Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0"
>
> [Sun Jun 02 11:35:08.859778 2019] [core:error] [pid 17274] [client
> 87.138.223.233:38826] AH00037: Symbolic link not allowed or link
> target not accessible: /var/www/sellfam.com/public/minecraft/www
>
> I don't know what you mean by adding an alias to a directory section.
>
> Last night, I remembered I did get this to work once on a FreeBSD 4
> box back in 2000 where I made symbolic links to user home directories,
> but that was Apache 1.3 and it was compiled from source.  But some 10
> years later, from a Debian package, I never could get it to work and
> finally upgraded to a 160GB hard disk so there were some substantial
> changes to what was allowed by default.  The structure of Apache
> configuration was exploded into a complexity that I'd have to totally
> relearn everything since shutting my old webserver down.  It seems as
> if my old Piper Cub turned into a Boeing 727.
>
> On Sat, Jun 1, 2019 at 5:18 PM Eric Covener  wrote:
> >
> > > 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 FollowSymLinks   ###   <---  I did the same here too
> > Probably better to do +FollowSymlinks and not be implicitly unsetting
> > all other options.
> >
> > Finally, have you considered just adding an Alias and a corresponding
> >  section?
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> > For additional commands, e-mail: users-h...@httpd.apache.org
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>


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

2019-06-02 Thread timothylegg .
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 3852 "-" "Mozilla/5.0 (X11;
Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0"

[Sun Jun 02 11:35:08.859778 2019] [core:error] [pid 17274] [client
87.138.223.233:38826] AH00037: Symbolic link not allowed or link
target not accessible: /var/www/sellfam.com/public/minecraft/www

I don't know what you mean by adding an alias to a directory section.

Last night, I remembered I did get this to work once on a FreeBSD 4
box back in 2000 where I made symbolic links to user home directories,
but that was Apache 1.3 and it was compiled from source.  But some 10
years later, from a Debian package, I never could get it to work and
finally upgraded to a 160GB hard disk so there were some substantial
changes to what was allowed by default.  The structure of Apache
configuration was exploded into a complexity that I'd have to totally
relearn everything since shutting my old webserver down.  It seems as
if my old Piper Cub turned into a Boeing 727.

On Sat, Jun 1, 2019 at 5:18 PM Eric Covener  wrote:
>
> > 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 FollowSymLinks   ###   <---  I did the same here too
> Probably better to do +FollowSymlinks and not be implicitly unsetting
> all other options.
>
> Finally, have you considered just adding an Alias and a corresponding
>  section?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2019-06-01 Thread Eric Covener
> 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 FollowSymLinks   ###   <---  I did the same here too
Probably better to do +FollowSymlinks and not be implicitly unsetting
all other options.

Finally, have you considered just adding an Alias and a corresponding
 section?

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2019-06-01 Thread timothylegg .
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 too busy to deal with a reinstall this
month.

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.

I really don't understand the paranoia surrounding symlinks in the
first place...  It's not like people make them by accident; they are
also files and all files should be treated the same.  I just want this
to work, it doesn't have to be this hard.

##sellfam_com_80.conf

ServerAdmin webmaster@localhost
DocumentRoot /var/www/sellfam.com/public/
#   ### <--  This didn't work
 ###  <--neither did this
   Options FollowSymLinks   ###  <-- I told it to follow symbolic
links two different ways
   AllowOverride None

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
ServerName sellfam.com
ServerAlias www.sellfam.com
RewriteEngine on
RewriteCond %{SERVER_NAME} =www.sellfam.com [OR]
RewriteCond %{SERVER_NAME} =sellfam.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]


#sellfam_com_443.conf


ServerAdmin webmaster@localhost
DocumentRoot /var/www/sellfam.com/public/
#

Options FollowSymLinks   ###   <---  I did the same here too
AllowOverride None

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
ServerName sellfam.com
ServerAlias www.sellfam.com
Include /etc/letsencrypt/options-ssl-apache.conf
Include /etc/letsencrypt/options-ssl-apache.conf
Include /etc/letsencrypt/options-ssl-apache.conf
Include /etc/letsencrypt/options-ssl-apache.conf
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/sellfam.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/sellfam.com/privkey.pem



And look, the permissions can't be any more relaxed than this...

# ls -al minecraft/
total 12
drwxr-xr-x 2 www-data www-data 4096 Jun  1 16:04 .
drwxr-xr-x 6 www-data www-data 4096 Jun  1 15:57 ..
-rw-r--r-- 1 root root6 Jun  1 16:04 hello.txt
lrwxrwxrwx 1 www-data www-data   21 Jun  1 15:57 www -> /home/legg/extra/www/

I have the ownership correct too.

 ls -al /home/legg/extra/www
total 272
drwxr-xr-x 5 www-data www-data   4096 Jun  1 15:54 .
drwxrwxr-- 5 legg legg   4096 Jun  1 14:43 ..
-rw-r--r-- 1 www-data www-data 44 Jun  1 15:43 baseMarkers.js
-rw-r--r-- 1 www-data www-data631 Jun  1 15:43 bed.png
-rw-r--r-- 1 www-data www-data   3947 Jun  1 15:43 compass_lower-left.png
-rw-r--r-- 1 www-data www-data   3955 Jun  1 15:43 compass_lower-right.png
-rw-r--r-- 1 www-data www-data   3960 Jun  1 15:43 compass_upper-left.png
-rw-r--r-- 1 www-data www-data   3952 Jun  1 15:43 compass_upper-right.png
drwxr-xr-x 2 www-data www-data   4096 Jun  1 15:43 icons
drwxr-xr-x 2 www-data www-data   4096 Jun  1 15:43 images
-rw-r--r-- 1 www-data www-data   1013 Jun  1 15:43 index.html
-rw-r--r-- 1 www-data www-data  14198 Jun  1 15:43 leaflet.css
-rw-r--r-- 1 www-data www-data 139643 Jun  1 15:43 leaflet.js
-rw-r--r-- 1 www-data www-data   3255 Jun  1 15:43 overviewer.css
-rw-r--r-- 1 www-data www-data  40101 Jun  1 15:43 overviewer.js
-rw-r--r-- 1 www-data www-data   1977 Jun  1 15:43 overviewerConfig.js
-rw-r--r-- 1 www-data www-data714 Jun  1 15:43 regions.js
-rw-r--r-- 1 www-data www-data257 Jun  1 15:43 signpost-shadow.png
-rw-r--r-- 1 www-data www-data518 Jun  1 15:43 signpost.png
-rw-r--r-- 1 www-data www-data171 Jun  1 15:43 signpost_icon.png
drwx-- 6 www-data www-data   4096 Jun  1 15:27 world-lighting

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2019-02-06 Thread Daniel Ferradal
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

Require all denied


in virtualhost and for documentroot:


 DocumentRoot /path/do/docroot

###
# Other directives here


Require all granted




El mié., 6 feb. 2019 a las 6:03, Dan Ehrlich
() escribió:
>
> 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 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 page only loading without any issue. We are getting 403 Forbidden 
> Message on Rest of the Pages. Kindly please help how to enable permission to 
> all folder and its subfolders in 2.4.25.
>
> For Example:
> Working:
> http://domain.com/sites
>
> Notworking:
> http://domain.com/newsroom
> http://domain.com/events
> http://domain.com/about
> & Other pages
>
> RewriteEngine on
> RewriteRule ^/+$ /sites/  [R,L]
> DocumentRoot "/apps/apache2.4"
> 
> Options FollowSymLinks
> AllowOverride None
> Require all granted
> 



-- 
Daniel Ferradal
HTTPD Project
#httpd help at Freenode

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2019-02-05 Thread Dan Ehrlich
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 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 page only loading without any issue. We are getting 403 Forbidden 
> Message on Rest of the Pages. Kindly please help how to enable permission to 
> all folder and its subfolders in 2.4.25.
> 
> For Example:
> Working:
> http://domain.com/sites
> 
> Notworking:
> http://domain.com/newsroom
> http://domain.com/events
> http://domain.com/about
> & Other pages
> 
> RewriteEngine on
> RewriteRule ^/+$ /sites/  [R,L]
>   DocumentRoot "/apps/apache2.4"
> 
> Options FollowSymLinks
> AllowOverride None
>   Require all granted
> 


[users@httpd] 403 Forbidden Error on Apache 2.4

2019-02-05 Thread Jayaram Ponnusamy
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 page only loading without any issue. We are getting 403
Forbidden Message on Rest of the Pages. Kindly please help how to enable
permission to all folder and its subfolders in 2.4.25.

For Example:
Working:
http://domain.com/sites

Notworking:
http://domain.com/newsroom
http://domain.com/events
http://domain.com/about
& Other pages

RewriteEngine on
RewriteRule ^/+$ /sites/  [R,L]
DocumentRoot "/apps/apache2.4"

Options FollowSymLinks
AllowOverride None
Require all granted



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

2016-08-24 Thread Amit Agrawal88

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 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:\Git\Repos"
  
  Options All
  AllowOverride All
  Require all granted
  


There are not .httpaccess file in C:\Git\Repos so 'AllowOverride All' has
no effect, I could have kept it None as well. To begin with, I am just
trying to serve git repository over http and hence I have allowed access to
everybody.
The Env variable for Git has been set and all GET request ending with /git/
is redirected to git-http-backend.

  SetEnv GIT_PROJECT_ROOT "C:\Git\Repos"
  SetEnv GIT_HTTP_EXPORT_ALL
  ScriptAlias /git/ "C:/Program
  Files/Git/mingw64/libexec/git-core/git-http-backend/"
However, I get 403 Forbidden error when I try to clone the repository like
this
  C:\test>git clone http://localhost:80/git/Projects/example
  Cloning into 'example'...
  fatal: unable to access 'http://localhost:80/git/Projects/example/':
  The requested URL returned error: 403
. Following is the error in access log
  ::1 - - [22/Aug/2016:16:44:54 +0530] "GET /git/ HTTP/1.1" 403 213
Error in Error Log
  [client ::1:64266] AH01630: client denied by server configuration:
  C:/Program Files/Git/mingw64/libexec/git-core/git-http-backend
So it looks like git-http-backend is not allowing this access. As per the
documentation, it concatenates environment variables PATH_INFO with
GIT_PROJECT_ROOT which seems be correctly set. I also tried "AcceptPathInfo
On" but that didn't help.


I have been reading and trying lots of things like the ones mentioned below
including searching this forum to any solution to this but still in vain.
  
https://docs.moodle.org/31/en/Manual_install_on_Windows_7_with_Apache_and_MySQL#Step_4:_Configure_Apache_and_PHP

  https://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html

  http://www.parallelsymmetry.com/howto/git.jsp
I have tried to give location access to /git/ path but that didn't help
  
 AuthType Basic
 AuthName "Git Access"
 Require all granted
  
Also for all fetch requests
  
 AuthType Basic
 AuthName "Git Access"
 Require group committers
 ...
  

I also given Read/write access to C:\Git\Repos to ALL users in the system.
I am using Windows Server 2012 R2.

I have a feeling that either some of the above configuration is wrong OR
git-http-backend is expecting something which I have not set.

I have been trying to setup the access for last few days and above are just
few of things that I tried. Kindly help.

Please don't remove this post as I searched the forum already and didn't
come across any similar post with solution.

Regards,
Amit
  (See attached file: httpd.conf)

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2016-08-22 Thread Amit Agrawal88


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:\Git\Repos"
   
   Options All
   AllowOverride All
   Require all granted
   

There are not .httpaccess file in C:\Git\Repos so 'AllowOverride All' has
no effect, I could have kept it None as well. To begin with, I am just
trying to serve git repository over http and hence I have allowed access to
everybody.
The Env variable for Git has been set and all GET request ending with /git/
is redirected to git-http-backend.

   SetEnv GIT_PROJECT_ROOT "C:\Git\Repos"
   SetEnv GIT_HTTP_EXPORT_ALL
   ScriptAlias /git/ "C:/Program
   Files/Git/mingw64/libexec/git-core/git-http-backend/"

However, I get 403 Forbidden error when I try to clone the repository like
this
   C:\test>git clone http://localhost:80/git/Projects/example
   Cloning into 'example'...
   fatal: unable to access 'http://localhost:80/git/Projects/example/': The
   requested URL returned error: 403

. Following is the error in access log
   ::1 - - [22/Aug/2016:16:44:54 +0530] "GET /git/ HTTP/1.1" 403 213

Error in Error Log
   [client ::1:64266] AH01630: client denied by server configuration:
   C:/Program Files/Git/mingw64/libexec/git-core/git-http-backend

So it looks like git-http-backend is not allowing this access. As per the
documentation, it concatenates environment variables PATH_INFO with
GIT_PROJECT_ROOT which seems be correctly set. I also tried "AcceptPathInfo
On" but that didn't help.


I have been reading and trying lots of things  like the ones mentioned
below including searching this forum to any solution to this but still in
vain.
   
https://docs.moodle.org/31/en/Manual_install_on_Windows_7_with_Apache_and_MySQL#Step_4:_Configure_Apache_and_PHP
   https://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
   http://www.parallelsymmetry.com/howto/git.jsp

I have tried to give location access to /git/ path but that didn't help
   
   AuthType Basic
   AuthName "Git Access"
   Require all granted
   
Also for all fetch requests

   
   AuthType Basic
   AuthName "Git Access"
   Require group committers
   ...
   

I also given Read/write access to C:\Git\Repos to ALL users in the system.
I am using Windows Server 2012 R2.

I have a feeling that either some of the above configuration is wrong OR
git-http-backend is expecting something which I have not set.

I have been trying to setup the access for last few days and above are just
few of things that I tried. Kindly help.

Please don't remove this post as I searched the forum already and didn't
come across any similar post with solution.

Regards,
Amit
   (See attached file: httpd.conf)


httpd.conf
Description: Binary data

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] 403 Forbidden

2016-07-06 Thread newlifeR REN
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(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:
>
>
> What does your ErrorLog say?  Did you update your httpd.conf as
> Administrator?
>
> --
> Eric Covener
> cove...@gmail.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>


apache_error.log
Description: Binary data


httpd.conf
Description: Binary data

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] 403 Forbidden

2016-07-06 Thread Eric Covener
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 same error 403:


What does your ErrorLog say?  Did you update your httpd.conf as Administrator?

-- 
Eric Covener
cove...@gmail.com

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



[users@httpd] 403 Forbidden

2016-07-06 Thread newlifeR REN
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"

#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI
MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important.  Please see
# http://httpd.apache.org/docs/2.4/mod/core.html#options
# for more information.
#
Options +Indexes +FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess
files.
# It can be "All", "None", or any combination of the keywords:
#   AllowOverride FileInfo AuthConfig Limit
#
AllowOverride all

#
# Controls who can get stuff from this server.
#

#   onlineoffline tag - don't remove
 Require all granted



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

2015-04-27 Thread Thomas DEBESSE
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/null -I -w '%{http_code}' '
http://domain/script.php?action=Mettre+à+jour
'
302

But with unicode urlencoded characters it does not works:

user@system:~$ curl -s -o /dev/null -I -w '%{http_code}' '
http://domain/script.php?action=Mettre+%C3%A0+jour'
403

As you see, the error message wrongly complain about the file path, since
the problem is in the GET parameters:

user@system:~$ curl 'http://domain/script.php?action=Mettre+%C3%A0+jour' |
html2text
** Forbidden **
You don't have permission to access /script.php on this server.


Also, when this kind of 403 error happens, the Apache's error log is empty…

Some people are talking about this problem on the web, but they are so few
and it's hard to find an usable answer:
http://stackoverflow.com/questions/4862781/apache-escaped-umlauts-in-query-string-url-lead-to-403

Here I found a fix, but I don't understand what happens and what it does
and if it's safe to use, can you say if this fix is safe to use?
https://wordpress.org/support/topic/strange-403-or-404-forbidden-errors-with-wordpress

This guy does:


SecFilterEngine Off
SecFilterScanPOST Off


So this guy explicitely disabled some security options, is disabling some
security options the only way to get unicode urlencoded GET parameters?

Since you now know which symptom I get and wich option changes the
behavior, do you know what happens? Is this a bug?

Thanks in advance.

PS: I'm using Apache 2.2.22 on Debian 7 Wheezy.

--
Thomas DEBESSE


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

2012-11-13 Thread Lester Caine

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 added the
hard coded paths to the re-write rules.

So now the question is "Is there something I can use to add the vhost
path automatically in the generic config file?"


Well, how did you fix it?! :P

As for your new question, we're not mind-readers... we'd need to see the
mod_rewrite rules to provide a meaningful answer.


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 using the DocumentRoot setting



Right; as you suggested earlier, this seems to be a product of moving
your mod_rewrite rules from .htaccess files to vhost configuration files.


Except that was done for and is working on 2.2 ...


From what I can tell, the only portion of that path that needs to

dynamic is the host name.

I don't know if this will work in that context, but given that your
filesystem structure uses the host name, perhaps you could use
%{HTTP_HOST} in place of "eveshamtc.org.uk", e.g.:


Some domains share the one directory so that one will be difficult in all cases!


RewriteRule ^/?wiki/view/(.+)$
/srv/website/%{$HTTP_HOST}/wiki/index.php?page=$1 [L]


I will give it a try ... although the alternative which Yehuda is pointing 
towards is to include the generic rewrite script within the  section 
of the  section. However there are a group of .conf files loaded for the 
generic setup, and some of them should not be loaded then. This all seems rather 
messy when the current set-up works perfectly on 2.2 :(


Currently I just edit the one rewrite config file and update all sites ...

--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Ben Johnson


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 paths to the re-write rules.
>>> >
>>> >So now the question is "Is there something I can use to add the vhost
>>> >path automatically in the generic config file?"
>>> >
>> Well, how did you fix it?! :P
>>
>> As for your new question, we're not mind-readers... we'd need to see the
>> mod_rewrite rules to provide a meaningful answer.
> 
> 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 using the DocumentRoot setting
> 

Right; as you suggested earlier, this seems to be a product of moving
your mod_rewrite rules from .htaccess files to vhost configuration files.

>From what I can tell, the only portion of that path that needs to
dynamic is the host name.

I don't know if this will work in that context, but given that your
filesystem structure uses the host name, perhaps you could use
%{HTTP_HOST} in place of "eveshamtc.org.uk", e.g.:

RewriteRule ^/?wiki/view/(.+)$
/srv/website/%{$HTTP_HOST}/wiki/index.php?page=$1 [L]

-Ben

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Lester Caine

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-path to a resource' is not using the DocumentRoot setting


That's a good point. Sorry it's a long thread and I thought I read in one of
your posts that the rewritre rules are properly mapping so I have excluded
mod_rewrite from the picture.


The 'DocumentRoot' element is not displayed in the rewrite log on the 2.2 
version which is working fine. So I ASSUMED the fact that the 2.4 version was 
working the same ...


So where do I report this problem. As far as I can see this IS a bug?

--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Yehuda Katz
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 using the DocumentRoot setting


I heard the same issue from someone else. While the documentation has not
changed from 2.2, I am wondering if it is now being done differently in 2.4.

First: The reason you had a change when you modified the 
require directive is because it was trying to match against /wiki on the
file system. (Note that a URL-path will be interpreted as a file-system
path is such a file exists. Do you have a /wiki folder? Or, might 2.4 not
be checking that properly?)
You could probably drop the leading slash and it would work (my only dev
server on 2.4 is Windows, so no guarantee that it is the same).
Have a look at the grey boxes at the top of
http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewriterule that
explain how per-directory rules are processed, particularly the third point
in the second box: the per-directory prefix is only added to the result for
rules that are in a  block or .htaccess, not for other
containers.


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

2012-11-13 Thread Igor Cicimov
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 added the
>>> >hard coded paths to the re-write rules.
>>> >
>>> >So now the question is "Is there something I can use to add the vhost
>>> >path automatically in the generic config file?"
>>> >
>>>
>> Well, how did you fix it?! :P
>>
>> As for your new question, we're not mind-readers... we'd need to see the
>> mod_rewrite rules to provide a meaningful answer.
>>
>
> 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 using the DocumentRoot setting
>
>
That's a good point. Sorry it's a long thread and I thought I read in one
of your posts that the rewritre rules are properly mapping so I have
excluded mod_rewrite from the picture.


> --
> Lester Caine - G8HFL
> -
> Contact - 
> http://lsces.co.uk/wiki/?page=**contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - 
> http://rainbowdigitalmedia.co.**uk
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@httpd.**apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>


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

2012-11-13 Thread Lester Caine

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 is "Is there something I can use to add the vhost
>path automatically in the generic config file?"
>

Well, how did you fix it?! :P

As for your new question, we're not mind-readers... we'd need to see the
mod_rewrite rules to provide a meaningful answer.


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 using the DocumentRoot setting

--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Lester Caine

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 permissions of the wiki directory on the old and the
new server and make sure they are identical.


Igor - you are missing some earlier information ... the site works perfectly 
when 'directly' accessing the content, so permissions are not a problem! I have 
now identified what IS different - don't understand why - but currently it looks 
like have to manually rewrite every vhost file as 2.4 is simply not including 
the 'DocumentRoot' value in the same way it is included on 2.2 :(


--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Ben Johnson


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 paths in this way
>> should be scorned, publicly. But that's here nor there.
> 
> http://evesham.uk.com/wiki/Life+In+Evesham is working ... :)
> 
> But now I need to work out how to get the 'generic' code I've been using
> for years to work.
> 
> 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 is "Is there something I can use to add the vhost
> path automatically in the generic config file?"
> 

Well, how did you fix it?! :P

As for your new question, we're not mind-readers... we'd need to see the
mod_rewrite rules to provide a meaningful answer.

-Ben

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Lester Caine

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 that's here nor there.


http://evesham.uk.com/wiki/Life+In+Evesham is working ... :)

But now I need to work out how to get the 'generic' code I've been using for 
years to work.


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 is "Is there something I can use to add the vhost path 
automatically in the generic config file?"


--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Igor Cicimov
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 making sense Ben - Thanks for the pointers
>
> This is one of many 'bitweaver' based sites some of which have been
> running on a number of Apache 2.2 machines for many years - without a
> problem. It's having moved them to a new 2.4 based machine that is causing
> the problem!
>
>
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 permissions of the wiki directory on the old and
the new server and make sure they are identical.


> But this all configured in the vhost.d files, so
> RewriteBase: only valid in per-directory config files
>
> I've avoided using .htaccess so far as I thought THAT was frond on? Am I
> going to have to switch everything back to directory based, having spent a
> lot of time stripping it on 2.2 :(
>
>
> --
> Lester Caine - G8HFL
> -
> Contact - 
> http://lsces.co.uk/wiki/?page=**contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - 
> http://rainbowdigitalmedia.co.**uk
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@httpd.**apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>


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

2012-11-13 Thread Lester Caine

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' based sites some of which have been running on a 
number of Apache 2.2 machines for many years - without a problem. It's having 
moved them to a new 2.4 based machine that is causing the problem!


But this all configured in the vhost.d files, so
RewriteBase: only valid in per-directory config files

I've avoided using .htaccess so far as I thought THAT was frond on? Am I going 
to have to switch everything back to directory based, having spent a lot of time 
stripping it on 2.2 :(


--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Ben Johnson


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.
> 
>> mod_info is now loaded, but currently I'm just flipping to home page
>>  just
>> working through the settings.
> Now working but locked down locally at present ...
> What should I be looking for.
> 
>> Just working through Yehuda's link as well.
> I've tried a few things from the mediawiki article but I suspect that is
> based on 2.2 working?
> 
> AH - found something!
> I've switched the deny off on the '/' level
> 
> From server-info -
> Current Configuration:
> In file: /opt/apache2/conf/httpd.conf
>  199: 
>  201:   Require all granted ( Was denied )
> : 
>  223: 
>  224:   Require all denied
> : 
>  315: 
>  318:   Require all granted
> : 
> In file: /opt/apache2/conf/vhosts.d/25_vhost.eveshamtc.org.uk.conf
>   60:   
>   73: Options FollowSymLinks
>   80: AllowOverride All
> :   
>   94:   ErrorDocument 404 /index.php
> : 
> 
> AND THEN I GET
> Warning: require_once(../kernel/setup_inc.php): failed to open stream:
> No such file or directory in /wiki/index.php on line 16 Fatal error:
> require_once(): Failed opening required '../kernel/setup_inc.php'
> (include_path='.:/opt/php5/lib/php:/opt/php5/lib/php/PEAR') in
> /wiki/index.php on line 16
> 
> Which is telling me that the rewrite has lost the local directory
> details for the vhost ... Or at least I think that is the problem?
> 

Are you defining a RewriteBase amongst your mod_rewrite rule(s)? If so,
what is the value?

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 that's here nor there.

Fundamentally, it seems the problem is that the require_once() statement
on line 16 of index.php is looking for setup_inc.php "up one level and
inside the 'kernel' directory". But given your URL structure, "up one
level" references the vhost's document root, and most certainly, there
is no "kernel" directory at that location. Presumably, the "kernel"
directory is inside the "wiki" directory.

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?

-Ben

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Igor Cicimov
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 no change to the 403 error on rewrite results.
>>
>>> mod_info is now loaded, but currently I'm just flipping to home page
 just
>>> working through the settings.
>>
>> Now working but locked down locally at present ...
>> What should I be looking for.
>>
>>> Just working through Yehuda's link as well.
>>
>> I've tried a few things from the mediawiki article but I suspect that is
based on 2.2 working?
>>
>> AH - found something!
>> I've switched the deny off on the '/' level
>>
>> From server-info -
>> Current Configuration:
>> In file: /opt/apache2/conf/httpd.conf
>>  199: 
>>  201:   Require all granted ( Was denied )
>> : 
>>  223: 
>>  224:   Require all denied
>> : 
>>  315: 
>>  318:   Require all granted
>> : 
>> In file: /opt/apache2/conf/vhosts.d/25_vhost.eveshamtc.org.uk.conf
>>   60:   
>>   73: Options FollowSymLinks
>>   80: AllowOverride All
>> :   
>>   94:   ErrorDocument 404 /index.php
>> : 
>>
>> AND THEN I GET
>> Warning: require_once(../kernel/setup_inc.php): failed to open stream:
No such file or directory in /wiki/index.php on line 16 Fatal error:
require_once(): Failed opening required '../kernel/setup_inc.php'
(include_path='.:/opt/php5/lib/php:/opt/php5/lib/php/PEAR') in
/wiki/index.php on line 16
>>
>> Which is telling me that the rewrite has lost the local directory
details for the vhost ... Or at least I think that is the problem?
>>
>
> No, PHP include errors have typically no cause in apache misconfiguration.
>
>
> --
> J.
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>

First on which os are you running on? Have you checked the file
permissions? Does MediaWiki come with its one apache config file? What
happens if you put Options +Indexes for the wiki directory?


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

2012-11-13 Thread Jeroen Geilman

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 is now loaded, but currently I'm just flipping to home page 
 just

working through the settings.

Now working but locked down locally at present ...
What should I be looking for.


Just working through Yehuda's link as well.
I've tried a few things from the mediawiki article but I suspect that 
is based on 2.2 working?


AH - found something!
I've switched the deny off on the '/' level

From server-info -
Current Configuration:
In file: /opt/apache2/conf/httpd.conf
 199: 
 201:   Require all granted ( Was denied )
: 
 223: 
 224:   Require all denied
: 
 315: 
 318:   Require all granted
: 
In file: /opt/apache2/conf/vhosts.d/25_vhost.eveshamtc.org.uk.conf
  60:   
  73: Options FollowSymLinks
  80: AllowOverride All
:   
  94:   ErrorDocument 404 /index.php
: 

AND THEN I GET
Warning: require_once(../kernel/setup_inc.php): failed to open stream: 
No such file or directory in /wiki/index.php on line 16 Fatal error: 
require_once(): Failed opening required '../kernel/setup_inc.php' 
(include_path='.:/opt/php5/lib/php:/opt/php5/lib/php/PEAR') in 
/wiki/index.php on line 16


Which is telling me that the rewrite has lost the local directory 
details for the vhost ... Or at least I think that is the problem?




No, PHP include errors have typically no cause in apache misconfiguration.


--
J.


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Lester Caine

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 flipping to home page  just
working through the settings.

Now working but locked down locally at present ...
What should I be looking for.


Just working through Yehuda's link as well.
I've tried a few things from the mediawiki article but I suspect that is based 
on 2.2 working?


AH - found something!
I've switched the deny off on the '/' level

From server-info -
Current Configuration:
In file: /opt/apache2/conf/httpd.conf
 199: 
 201:   Require all granted ( Was denied )
: 
 223: 
 224:   Require all denied
: 
 315: 
 318:   Require all granted
: 
In file: /opt/apache2/conf/vhosts.d/25_vhost.eveshamtc.org.uk.conf
  60:   
  73: Options FollowSymLinks
  80: AllowOverride All
:   
  94:   ErrorDocument 404 /index.php
: 

AND THEN I GET
Warning: require_once(../kernel/setup_inc.php): failed to open stream: No such 
file or directory in /wiki/index.php on line 16 Fatal error: require_once(): 
Failed opening required '../kernel/setup_inc.php' 
(include_path='.:/opt/php5/lib/php:/opt/php5/lib/php/PEAR') in /wiki/index.php 
on line 16


Which is telling me that the rewrite has lost the local directory details for 
the vhost ... Or at least I think that is the problem?


--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Lester Caine

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+Evesham directly, right?

http://evesham.uk.com/wiki/index.php?page=Life+In+Evesham works fine
As does http://evesham.uk.com/wiki/index.php loading the home page.
But I do agree that mod_rewrite does seem to have done the right job!


Regarding mod_info, while I have not tested this with Apache 2.4, it
should be as simple as installing the module and adding something like
this to your server configuration:



Require all granted
SetHandler server-info



You'll probably want to add some kind of authentication requirement to
the  block, too, so that unauthorized parties cannot view your
configuration directives.
mod_info is now loaded, but currently I'm just flipping to home page  just 
working through the settings.

Just working through Yehuda's link as well.

--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Ben Johnson


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 conversion from
> http://evesham.uk.com/wiki/Life+in+Evesham
> to
> http://evesham.uk.com/wiki/index.php?page=Life+in+Evesham
> 
> The full format works fine, it's what is being used now as the site is
> live.
> With the 'LogLevel alert rewrite:trace5' commented out I get
> 
> [Fri Nov 09 17:46:24.546411 2012] [authz_core:error] [pid 18394:tid
> 140678935852800] [client 81.138.11.136:47676] AH01630: client denied by
> server configuration: /wiki/index.php
> 
> Which I presume IS the fault I'm trying to clear?
> 
> Enabling the Loglevel setting I get
> 
> [Fri Nov 09 17:46:43.310846 2012] [rewrite:trace2] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - -
> [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] init rewrite
> engine with requested uri /wiki/Location+and+Travel
> [Fri Nov 09 17:46:43.310894 2012] [rewrite:trace3] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - -
> [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] applying
> pattern '^.*$' to uri '/wiki/Location+and+Travel'
> [Fri Nov 09 17:46:43.310969 2012] [rewrite:trace3] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - -
> [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] applying
> pattern '^/wiki/view/(.+)$' to uri '/wiki/Location+and+Travel'
> [Fri Nov 09 17:46:43.310993 2012] [rewrite:trace3] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - -
> [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] applying
> pattern '^/wiki/(.+)$' to uri '/wiki/Location+and+Travel'
> [Fri Nov 09 17:46:43.311026 2012] [rewrite:trace2] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - -
> [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] rewrite
> '/wiki/Location+and+Travel' -> '/wiki/index.php?page=Location+and+Travel'
> [Fri Nov 09 17:46:43.311047 2012] [rewrite:trace3] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - -
> [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] split
> uri=/wiki/index.php?page=Location+and+Travel -> uri=/wiki/index.php,
> args=page=Location+and+Travel
> [Fri Nov 09 17:46:43.311067 2012] [rewrite:trace2] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - -
> [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] local path
> result: /wiki/index.php
> [Fri Nov 09 17:46:43.311089 2012] [rewrite:trace1] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - -
> [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] go-ahead
> with /wiki/index.php [OK]
> 
> At which point I asked for some help ... I think I've checked everything
> against the http://httpd.apache.org/docs/2.4/upgrading.html#run-time
> crib sheet and I can get the site to give the right errors when I make a
> mistake but I am now lost as to where to go next.
> 
> mod_info should be running, but I'm not seeing it currently  still
> working on this.
> 

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+Evesham directly, right?

Regarding mod_info, while I have not tested this with Apache 2.4, it
should be as simple as installing the module and adding something like
this to your server configuration:



Require all granted
SetHandler server-info



You'll probably want to add some kind of authentication requirement to
the  block, too, so that unauthorized parties cannot view your
configuration directives.

-Ben

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Yehuda Katz
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 when I hit
http://evesham.uk.com/index.php?page=Life+in+Evesham).
Oddly enough, when I go to http://evesham.uk.com/Life+in+Evesham, I get
your home page.

I think MediaWiki recommends installing in /w/ (or at least something
different than the rewrite prefix you will be using)
http://www.mediawiki.org/wiki/Manual:Short_URL/Apache
Edits have been made to that page as recently as the beginning of October,
so you might want to have a look there.

- Y

On Tue, Nov 13, 2012 at 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 conversion from
> http://evesham.uk.com/wiki/**Life+in+Evesham
> to
> http://evesham.uk.com/wiki/**index.php?page=Life+in+Evesham
>
> The full format works fine, it's what is being used now as the site is
> live.
> With the 'LogLevel alert rewrite:trace5' commented out I get
>
> [Fri Nov 09 17:46:24.546411 2012] [authz_core:error] [pid 18394:tid
> 140678935852800] [client 81.138.11.136:47676] AH01630: client denied by
> server configuration: /wiki/index.php
>
> Which I presume IS the fault I'm trying to clear?
>
> Enabling the Loglevel setting I get
>
> [Fri Nov 09 17:46:43.310846 2012] [rewrite:trace2] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - - [evesham.uk.com/sid#**7ff26e320370][rid#**
> 7ff26e6900a0/initial]
> init rewrite engine with requested uri /wiki/Location+and+Travel
> [Fri Nov 09 17:46:43.310894 2012] [rewrite:trace3] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - - [evesham.uk.com/sid#**7ff26e320370][rid#**
> 7ff26e6900a0/initial]
> applying pattern '^.*$' to uri '/wiki/Location+and+Travel'
> [Fri Nov 09 17:46:43.310969 2012] [rewrite:trace3] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - - [evesham.uk.com/sid#**7ff26e320370][rid#**
> 7ff26e6900a0/initial]
> applying pattern '^/wiki/view/(.+)$' to uri '/wiki/Location+and+Travel'
> [Fri Nov 09 17:46:43.310993 2012] [rewrite:trace3] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - - [evesham.uk.com/sid#**7ff26e320370][rid#**
> 7ff26e6900a0/initial]
> applying pattern '^/wiki/(.+)$' to uri '/wiki/Location+and+Travel'
> [Fri Nov 09 17:46:43.311026 2012] [rewrite:trace2] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - - [evesham.uk.com/sid#**7ff26e320370][rid#**
> 7ff26e6900a0/initial]
> rewrite '/wiki/Location+and+Travel' -> '/wiki/index.php?page=**
> Location+and+Travel'
> [Fri Nov 09 17:46:43.311047 2012] [rewrite:trace3] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - - [evesham.uk.com/sid#**7ff26e320370][rid#**
> 7ff26e6900a0/initial]
> split uri=/wiki/index.php?page=**Location+and+Travel ->
> uri=/wiki/index.php, args=page=Location+and+Travel
> [Fri Nov 09 17:46:43.311067 2012] [rewrite:trace2] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - - [evesham.uk.com/sid#**7ff26e320370][rid#**
> 7ff26e6900a0/initial]
> local path result: /wiki/index.php
> [Fri Nov 09 17:46:43.311089 2012] [rewrite:trace1] [pid 18791:tid
> 140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686]
> 81.138.11.136 - - [evesham.uk.com/sid#**7ff26e320370][rid#**
> 7ff26e6900a0/initial]
> go-ahead with /wiki/index.php [OK]
>
> At which point I asked for some help ... I think I've checked everything
> against the 
> http://httpd.apache.org/docs/**2.4/upgrading.html#run-timecrib
>  sheet and I can get the site to give the right errors when I make a
> mistake but I am now lost as to where to go next.
>
> mod_info should be running, but I'm not seeing it curre

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

2012-11-13 Thread Lester Caine

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+Evesham
to
http://evesham.uk.com/wiki/index.php?page=Life+in+Evesham

The full format works fine, it's what is being used now as the site is live.
With the 'LogLevel alert rewrite:trace5' commented out I get

[Fri Nov 09 17:46:24.546411 2012] [authz_core:error] [pid 18394:tid 
140678935852800] [client 81.138.11.136:47676] AH01630: client denied by server 
configuration: /wiki/index.php


Which I presume IS the fault I'm trying to clear?

Enabling the Loglevel setting I get

[Fri Nov 09 17:46:43.310846 2012] [rewrite:trace2] [pid 18791:tid 
140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686] 81.138.11.136 
- - [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] init rewrite 
engine with requested uri /wiki/Location+and+Travel
[Fri Nov 09 17:46:43.310894 2012] [rewrite:trace3] [pid 18791:tid 
140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686] 81.138.11.136 
- - [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] applying pattern 
'^.*$' to uri '/wiki/Location+and+Travel'
[Fri Nov 09 17:46:43.310969 2012] [rewrite:trace3] [pid 18791:tid 
140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686] 81.138.11.136 
- - [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] applying pattern 
'^/wiki/view/(.+)$' to uri '/wiki/Location+and+Travel'
[Fri Nov 09 17:46:43.310993 2012] [rewrite:trace3] [pid 18791:tid 
140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686] 81.138.11.136 
- - [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] applying pattern 
'^/wiki/(.+)$' to uri '/wiki/Location+and+Travel'
[Fri Nov 09 17:46:43.311026 2012] [rewrite:trace2] [pid 18791:tid 
140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686] 81.138.11.136 
- - [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] rewrite 
'/wiki/Location+and+Travel' -> '/wiki/index.php?page=Location+and+Travel'
[Fri Nov 09 17:46:43.311047 2012] [rewrite:trace3] [pid 18791:tid 
140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686] 81.138.11.136 
- - [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] split 
uri=/wiki/index.php?page=Location+and+Travel -> uri=/wiki/index.php, 
args=page=Location+and+Travel
[Fri Nov 09 17:46:43.311067 2012] [rewrite:trace2] [pid 18791:tid 
140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686] 81.138.11.136 
- - [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] local path 
result: /wiki/index.php
[Fri Nov 09 17:46:43.311089 2012] [rewrite:trace1] [pid 18791:tid 
140678944245504] mod_rewrite.c(466): [client 81.138.11.136:47686] 81.138.11.136 
- - [evesham.uk.com/sid#7ff26e320370][rid#7ff26e6900a0/initial] go-ahead with 
/wiki/index.php [OK]


At which point I asked for some help ... I think I've checked everything against 
the http://httpd.apache.org/docs/2.4/upgrading.html#run-time crib sheet and I 
can get the site to give the right errors when I make a mistake but I am now 
lost as to where to go next.


mod_info should be running, but I'm not seeing it currently  still working 
on this.


--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Yehuda Katz
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 ...

2012-11-13 Thread Yehuda Katz
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 which
>> you might be receiving "client denied by server configuration" and not
>> all of them are obvious. Even to an expert.
>>
>
> Thanks for the nudge ... since this has all been running for years on 2.2
> I had hoped that it was just something I had not changed on the 2.4 setup?


The list of "all" the configuration changes required in core and some
included modules from 2.2 to 2.4 is here:
http://httpd.apache.org/docs/2.4/upgrading.html#run-time
I would also recommend mod_info if you can install it.

Also note that the RewriteLog config is not in 2.4. The new config is here:
http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#logging


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

2012-11-13 Thread Kevin A. McGrail

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 receiving "client denied by server configuration" and not
all of them are obvious. Even to an expert.


Thanks for the nudge ... since this has all been running for years on 
2.2 I had hoped that it was just something I had not changed on the 
2.4 setup?



This might be helpful in determining the error:

http://imgur.com/gallery/CGKLA

Regards,
KAM

P.S. OK it's not helpful at all but I couldn't resist posting it.  The cuteness 
overwhelmed me.


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Lester Caine

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" and not
all of them are obvious. Even to an expert.


Thanks for the nudge ... since this has all been running for years on 2.2 I had 
hoped that it was just something I had not changed on the 2.4 setup?


--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Antonio Vidal Ferrer
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 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/wiki/index.php?page=Life+in+Evesham

However there is a generic mod_rewrite for the machine in mod_rewrite.conf which
should allow http://eveshamtc.lsces.co.uk/wiki/Life+in+Evesham to work. The log
file is showing it being remapped to /wiki/index.php?page=Life+in+Evesham
but I'm getting a 'You don't have permission to access /wiki/Location+and+Travel
on this server.' error.

If I remove the LogLevel alert rewrite:trace3 then I'm getting a
AH01630: client denied by server configuration: /wiki/index.php

I've got
  Options All
  AllowOverride All
  Require all granted
But only the last should be required

So what am I missing to make this work on httpd2.4 ?

So is NOBODY seeing this problem?
I have the site live without re-write, so is it simply a matter of throwing
httpd 2.4 into the bin and going back to 2.2? Now was the ideal opportunity to
switch, but if something as basic as this is not working then is 2.4 actually
any use at all?



-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Ben Johnson


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://eveshamtc.lsces.co.uk/lifeinevesham.aspx is redirected to
>> http://eveshamtc.lsces.co.uk/wiki/index.php?page=Life+in+Evesham
>>
>> However there is a generic mod_rewrite for the machine in
>> mod_rewrite.conf which
>> should allow http://eveshamtc.lsces.co.uk/wiki/Life+in+Evesham to
>> work. The log
>> file is showing it being remapped to /wiki/index.php?page=Life+in+Evesham
>> but I'm getting a 'You don't have permission to access
>> /wiki/Location+and+Travel
>> on this server.' error.
>>
>> If I remove the LogLevel alert rewrite:trace3 then I'm getting a
>> AH01630: client denied by server configuration: /wiki/index.php
>>
>> I've got
>>  Options All
>>  AllowOverride All
>>  Require all granted
>> But only the last should be required
>>
>> So what am I missing to make this work on httpd2.4 ?
> 
> So is NOBODY seeing this problem?
> I have the site live without re-write, so is it simply a matter of
> throwing httpd 2.4 into the bin and going back to 2.2? Now was the ideal
> opportunity to switch, but if something as basic as this is not working
> then is 2.4 actually any use at all?
> 

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" and not
all of them are obvious. Even to an expert.

-Ben

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2012-11-13 Thread Lester Caine

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://eveshamtc.lsces.co.uk/wiki/index.php?page=Life+in+Evesham

However there is a generic mod_rewrite for the machine in mod_rewrite.conf which
should allow http://eveshamtc.lsces.co.uk/wiki/Life+in+Evesham to work. The log
file is showing it being remapped to /wiki/index.php?page=Life+in+Evesham
but I'm getting a 'You don't have permission to access /wiki/Location+and+Travel
on this server.' error.

If I remove the LogLevel alert rewrite:trace3 then I'm getting a
AH01630: client denied by server configuration: /wiki/index.php

I've got
 Options All
 AllowOverride All
 Require all granted
But only the last should be required

So what am I missing to make this work on httpd2.4 ?


So is NOBODY seeing this problem?
I have the site live without re-write, so is it simply a matter of throwing 
httpd 2.4 into the bin and going back to 2.2? Now was the ideal opportunity to 
switch, but if something as basic as this is not working then is 2.4 actually 
any use at all?


--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



[users@httpd] 403 Forbidden ...

2012-11-09 Thread Lester Caine

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


However there is a generic mod_rewrite for the machine in mod_rewrite.conf which 
should allow http://eveshamtc.lsces.co.uk/wiki/Life+in+Evesham to work. The log 
file is showing it being remapped to /wiki/index.php?page=Life+in+Evesham
but I'm getting a 'You don't have permission to access /wiki/Location+and+Travel 
on this server.' error.


If I remove the LogLevel alert rewrite:trace3 then I'm getting a
AH01630: client denied by server configuration: /wiki/index.php

I've got
Options All
AllowOverride All
Require all granted
But only the last should be required

So what am I missing to make this work on httpd2.4 ?

--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



[users@httpd] 403 forbidden

2012-09-16 Thread Crne We
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).