Hello all
I am gettting the following error below in bold during my make install.
What is the source path/target path which I need to create the symlink
with?
Below is my entire output from the make install command.
[root@nn250wb002 httpd-2.2.22]# make install
Making install in srclib
make[1]
Hello, I've been trying to track down an intermittent problem with a Java web
application that is running on tcServer fronted by Apache HTTP Server.We
get intermittent "Server Unavailable / HTTP 500" errors, and when we do see
them, there is the same set of log statements written to the Apac
We have seen an issue in httpd 2.2.21 where mod_cache incorrectly returns
HTTP 200 responses instead of HTTP 404 where:
- Reverse proxying is configured.
- ProxyErrorOverride is set to On.
- mod_disk_cache is set up to cache content proxied from mod_proxy.
- A local ErrorDocument 404 URL is config
Hi Jeff,
The version you have mentined below is available as 64-bit lib.
I will try my test with a 64bit version of apache.
Thanks,
~Abhi
- Original Message -
From: Jeff Trawick
To: users@httpd.apache.org
Cc:
Sent: Thursday, July 19, 2012 5:15 PM
Subject: Re: [users@httpd] A
Hi all.
Is it possible to have selective access to uploading-to/downloading-from a
WebDAV share, running in context of httpd?
That is, we want to implement a scenario, wherein some users have been
granted only uploading access; some users only download access; and some
both uploading-and-downloadi
- Original Message -
From: Jeff Trawick
To: users@httpd.apache.org
Cc:
Sent: Thursday, July 19, 2012 5:15 PM
Subject: Re: [users@httpd] Apache httpd 2.2.21 Segmentation faults
On Thu, Jul 19, 2012 at 7:32 AM, Abhi Auradkar wrote:
> Jeff,
>
> The cwmp handler has no functions lik
Le 2012-07-23 11:43, Noel Butler a écrit :
On Mon, 2012-07-23 at 06:12 +0200, ml wrote:
Firstly, it's not a good idea to just post to this group saying
"hey,
go read this URL" like above, as you can bet the majority here
wont
bother reading it as they are not to know if its malicious or n
On Mon, 2012-07-23 at 06:12 +0200, ml wrote:
> > Firstly, it's not a good idea to just post to this group saying "hey,
> > go read this URL" like above, as you can bet the majority here wont
> > bother reading it as they are not to know if its malicious or not.
> >
> > Instead place all relevant
