Hi all,
I'm having a problem with mod_mem_cache in Apache 2.0.58 where Apache
is sending back HTTP 304 incorrectly. This seems to happen
intermittently, about 1/8 requests if I hammer away on my server.
Here's my trace from wget - as you can see, there's no
If--Modified-Since or Etag header in
Hmmm ... I did this and it did not seem to work.
I deleted the user's account and home directory. I then re-added the users
account and home directory (all done by "useradd" and "userdel -d"
commands).
I then did the chown & chmod as described below. After uploading the
content, I get the messa
On 12/9/06, allan juul <[EMAIL PROTECTED]> wrote:
hi Joshua,
thanks for the quick reply
Joshua Slive wrote:
> On 12/9/06, allan juul <[EMAIL PROTECTED]> wrote:
>> how can one determine if a certain request is actually served from the
>> cache and not the backend from where it originally came fr
hi Joshua,
thanks for the quick reply
Joshua Slive wrote:
On 12/9/06, allan juul <[EMAIL PROTECTED]> wrote:
how can one determine if a certain request is actually served from the
cache and not the backend from where it originally came from ?
Check the Age HTTP response header. If the proxy
On 12/9/06, allan juul <[EMAIL PROTECTED]> wrote:
hello,
[win2003 / apache 2.2]
using mod_disk_cache and mod_rewrite we are trying to cache responses
with rarely updated but dynamic content served from a heavy loaded backend.
how can one determine if a certain request is actually served from
hello,
[win2003 / apache 2.2]
using mod_disk_cache and mod_rewrite we are trying to cache responses
with rarely updated but dynamic content served from a heavy loaded backend.
how can one determine if a certain request is actually served from the
cache and not the backend from where it
> Hello, apache2 hands off all requests to the interchange daemon via a
> socket. However, if a request is made like this:
>
> domain.com/location
>
> and the folder "location" exists at the docroot, apache2 appends a "/"
> character to the request before handing it off. Can I disable this
> beh
Thanks Christopher. Since I am still in the dev stage on this server, I think
I will simply delete the user account and home directory, then re-add the user,
set the permissions as you suggest, reload the test site content and give it a
go.
Thanks,
Scott
-Original Message-
From:
Steve Swift <[EMAIL PROTECTED]> wrote:
Long story short, I have added the vhost part to the httpd.conf and the
directory statement. I get the message in the error log that "Permission is
denied for /index.htm".
If anyone needs any additional information, please ask.
Please tell us what I
Linux filesystem permissions have three components, user, group, and
other. It should be possible to set the folder/file owner name to be the
user who is wanting to write/read files in the www folder using chown.
Then you can set the group for the folder to the group that the apache
process be
On 12/9/06, Grant <[EMAIL PROTECTED]> wrote:
Hello, apache2 hands off all requests to the interchange daemon via a
socket. However, if a request is made like this:
domain.com/location
and the folder "location" exists at the docroot, apache2 appends a "/"
character to the request before handing
Hi,
Thomas Antony <[EMAIL PROTECTED]> wrote:
and the user under the apache daemon is running needs read permissions
on the files and directories.
Can you show us how to change permissions or chmod in httpd.conf for Apache2
in Windows XP to avoid errors:
http://localhost/cgi-bin/hello1.e
Hello, apache2 hands off all requests to the interchange daemon via a
socket. However, if a request is made like this:
domain.com/location
and the folder "location" exists at the docroot, apache2 appends a "/"
character to the request before handing it off. Can I disable this
behavior? It is
Also, as a follow-up to my last reply, does anyone know of a simple howto that
covers this type of setup (ie: walks through the entire process)?
Thanks in advance,
Scott
-Original Message-
From: "Scott Hughes" <[EMAIL PROTECTED]>
Date: Sat, 9 Dec 2006 17:43:40
To:users@httpd.apache
Thanks for the response Steve!
A while after I sent this message I ran across a site that told me just that.
When it still didn't work, I realized it was also a directory permissions issue.
After working with the permissions (linux system) I was able to access the
pages.
Now I find that the u
Please make sure you are using the latest version of Apache and PHP (4.4.4),
as those are bug fix releases in order to make life in general easier. Not
to mention that PHP 4.3.9 has some incredibly huge security holes.
On 12/7/06, Cabbar Duzayak <[EMAIL PROTECTED]> wrote:
Before I start, I am u
Thomas is right, the resources he provides are excellent. You have to make
sure that DNS for domain1 and domain2 are pointing to your listener IP.
Sometimes I have seen ISPs or people forget to add in a record to have WWW
point to their IP as well.
If DNS is all correct and done and listening to
Just for my sake, couldn't a '-f /path/to/file' have avoided this problem?
On 12/7/06, Norman Peelman <[EMAIL PROTECTED]> wrote:
- Original Message -
From: "Gaming Mouse" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 07, 2006 4:28 AM
Subject: Re: [EMAIL PROTECTED] Changing DocumentR
Well, I'm still stuck.
sudo make clean
sudo ./configure --enable-modules=all --enable-mods-shared=all
--enable-ssl --enable-proxy --enable-deflate --prefix=/Library/Apache2
sudo make
sudo make install
sudo apachectl start
httpd: Syntax error on line 235 of /Library/Apache2/conf/httpd.conf: AP
I'm not a newbie, but this time I feel like one.
I have an executable on a web page (it's a Tight VNC server for PCs),
and when I attempt to select it, the web page directs me back to
127.0.0.1 - here's the log entry:
71.162.15.5 - - [09/Dec/2006:09:30:26 -0500] "GET
/tightvnc-1.2.9-setup.ex
Am Samstag, den 09.12.2006, 09:13 + schrieb Steve Swift:
> Each time you add a new place in your filesystem that will be
> referenced by apache, such as the DocumentRoot statement inside your
> virtual hosts blocks, you nearly always have to add a
> statement permitting access to that place.
> Listen 80
> NameVirtualHost 1.2.3.4:80
>
>
> DocumentRoot /home/os/html/domain1
> ServerName www.domain1.com
>
>
>
> DocumentRoot /home/os/html/domain2
> ServerName www.domain2.co.uk
>
>
Hi,
Which version of apache do you have installed?
What value does the ServerName directive for the
Each time you add a new place in your filesystem that will be referenced by
apache, such as the DocumentRoot statement inside your virtual hosts blocks,
you nearly always have to add a statement permitting access to
that place.
For example, I have:
Options Indexes FollowSymLinks
AllowOverr
23 matches
Mail list logo
