Joshua Slive wrote:
On 10/5/07, Hermidio A. Rodriguez Chavez <[EMAIL PROTECTED]> wrote:
Joshua Slive wrote:
What EXACTLY did you use for your HeaderName/ReadmeName configuration?
Do you understand the difference between the config with a leading
slash (where the Header/Readme is always taken
On 10/5/07, Hermidio A. Rodriguez Chavez <[EMAIL PROTECTED]> wrote:
> Joshua Slive wrote:
> > What EXACTLY did you use for your HeaderName/ReadmeName configuration?
> > Do you understand the difference between the config with a leading
> > slash (where the Header/Readme is always taken from the sa
Joshua Slive wrote:
On 10/5/07, Hermidio A. Rodriguez Chavez <[EMAIL PROTECTED]> wrote:
Hellow friends:
i like to configure one debian mirror and want to add HeaderName,
ReadMeName inside the virtual host, every things are ok at the first
page , but when i try access another directory inside th
On 10/5/07, Hermidio A. Rodriguez Chavez <[EMAIL PROTECTED]> wrote:
> Hellow friends:
>
> i like to configure one debian mirror and want to add HeaderName,
> ReadMeName inside the virtual host, every things are ok at the first
> page , but when i try access another directory inside the root folder
Hellow friends:
i like to configure one debian mirror and want to add HeaderName,
ReadMeName inside the virtual host, every things are ok at the first
page , but when i try access another directory inside the root folder
the files configure in this directive not work or can't see it, only
can see
Yup, that did the trick.
I got into this predicament in the first place because I was trying to
set up a default-content "hole" in a vhost served by mod_perl. That's
where the "SetHandler default" directive came from (it works for static
content like images and JavaScript). But when I set up
_cgi.c
mod_negotiation.c
mod_dir.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_rewrite.c
mod_so.c
I'm stumped. Has anyone else had this problem?
d
>
> ----
>
> Subject:
> Re: [EMAIL PROTECTED] mod_auto
On 12/13/06, David Scott <[EMAIL PROTECTED]> wrote:
David Scott wrote:
Nope, this simply does not work for me. Here is the latest httpd.conf
snippet:
Listen 3002
Alias /static /home/david/pix/html/static
DocumentRoot /home/david/pix/html
SetHandler default
Options
d_status.c
mod_autoindex.c
mod_asis.c
mod_cgi.c
mod_negotiation.c
mod_dir.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_rewrite.c
mod_so.c
I'm stumped. Has anyone else had this problem?
d
Subject:
Re: [
I *could* be wrong on this but don't you need an alias as well such as:
Alias /code "/home/david/pix/html/code"
Another way would be inside the VirtualHost directive and instead of
Location do:
SetHandler default
Order allow,deny
Allow from all
Options +Indexes +Follo
I've got apache 2.2.3 running and I'd like to generate an automatic
directory listing, but I can't. I've checked and mod_autoindex is
compiled in statically. The snippet from my httpd.conf is as follows.
I'd like a directory listing in the /code location.
Listen 3001
NameVirtualHost *:3001
On 6/30/06, Miguel Pagano <[EMAIL PROTECTED]> wrote:
On 6/30/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
> There was an old vaudeville joke that went something like:
> A man walks into the doctor's office, raises his arm and says, "Doc,
> it hurts when I do this." The doctor says, "Don't do that
On 6/30/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
There was an old vaudeville joke that went something like:
A man walks into the doctor's office, raises his arm and says, "Doc,
it hurts when I do this." The doctor says, "Don't do that."
Yes, there is a small bug here in the sense that Apache
On 6/30/06, Miguel Pagano <[EMAIL PROTECTED]> wrote:
Hi,
I discvorered a buggy behaviour in mod_autoindex: when the file
README.html is gzipped or compressed the content of that file is
showed after the directory listing. The problem is that the content of
the README file is gzipped or compressed
Hi,
I discvorered a buggy behaviour in mod_autoindex: when the file
README.html is gzipped or compressed the content of that file is
showed after the directory listing. The problem is that the content of
the README file is gzipped or compressed and is showed verbatim.
This problem is also mention
On 6/15/06, Emmanuel.Leguy <[EMAIL PROTECTED]> wrote:
Hello,
When i have directives which restrict access in a .htaccess file, i
can't list the directory in the upper directory. Is it normal?
Yes, it is normal. For security reasons, it is best not to display
restricted resources to the public
Hello,
When i have directives which restrict access in a .htaccess file, i
can't list the directory in the upper directory. Is it normal?
Ex:
in http://www.truc.fr/dir/child/ i have this .htaccess:
AuthType Basic
AuthName "restricted access"
AuthBasicAuthoritative off
require valid-user
If
17 matches
Mail list logo
