Re: [users@httpd] ScriptAlias/cgi-bin for apache instance on port 8080

You have probably put the python script in wrong directory. According to this: http://www.editrocket.com/articles/perl_apache_mac.html the default cgi one on OSX is */Library/WebServer/CGI-Executables * On Wed, Nov 14, 2012 at 3:19 PM, Tim Johnson wrote: > * Tim Johnson [121113 19:16]: > >

Re: [users@httpd] ScriptAlias/cgi-bin for apache instance on port 8080

* Tim Johnson [121113 19:16]: > I have an instance of apache listening on port 8080. > the following URL : > http://localhost:8080/cgi-bin/cgitest.py > returns a Not Found Error. > > I presume that I need a different virtualhost and scriptalias setup, > but am not sure how to accomplish this. >

[users@httpd] ScriptAlias/cgi-bin for apache instance on port 8080

I have an instance of apache listening on port 8080. the following URL : http://localhost:8080/cgi-bin/cgitest.py returns a Not Found Error. I presume that I need a different virtualhost and scriptalias setup, but am not sure how to accomplish this. URLs to documentation on this subject may suffi

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]

- Original Message - > Hello Experts - Can you advise on this error message? Application > seems to be having Intermittent issues. > > Proxy plugin generates following error : READ_ERROR_FROM_SERVER [os > error=0, line 841 of URL.cpp]: Unexpected EOF reading HTTP status – > failover requ

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]

Hello Experts - Can you advise on this error message? Application seems to be having Intermittent issues. Proxy plugin generates following error : READ_ERROR_FROM_SERVER [os error=0, line 841 of URL.cpp]: Unexpected EOF reading HTTP status – failover request based on Idempotent flag’ Thanks S

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