Hello,
Apache 2.2.14
Hello List,
have a question to ssl and two vhosts.
i have 2 ip-based vhosts for enabling ssl for one domain in httpd.conf
VirtualHost ip1.ip1.ip1.ip1:443
Servername example.com
SSLCertificateFile crt1
/VirtualHost
VirtualHost ip2.ip2.ip2.ip2:443
Dear Apache Users,
I have been looking at a problem for so many hours now that I think it
has made me blind.
The below configuration is intended to restrict access to /admin-cgi/ to
members of the group admin, which is defined in a plain text file,
whilst users and passwords are in a DBM
On 21 Feb 2011, at 09:12, Lee Goddard wrote:
Dear Apache Users,
I have been looking at a problem for so many hours now that I think it has
made me blind.
The below configuration is intended to restrict access to /admin-cgi/ to
members of the group admin, which is defined in a plain
Hi Nick,
On 21/02/2011 10:31, Nick Kew wrote:
Dear Apache Users,
I have been looking at a problem for so many hours now that I think it has made
me blind.
The below configuration is intended to restrict access to /admin-cgi/ to members of the
group admin, which is defined in a plain text
On 21/02/2011 10:31, Nick Kew wrote:
Dear Apache Users,
I have been looking at a problem for so many hours now that I think it has made
me blind.
The below configuration is intended to restrict access to /admin-cgi/ to members of the
group admin, which is defined in a plain text file,
On Mon, Feb 21, 2011 at 10:09 AM, Hajo Locke hajo.lo...@gmx.de wrote:
Nobody has an opinion about this issue? I think this is critical. Either a
bug in apache or a bug in my conf. my conf seems clean, i cannot solve this.
it should be impossible that apache is mixing vhost-special directives.
Nobody has an opinion about this issue? I think this is critical. Either a
bug in apache or a bug in my conf. my conf seems clean, i cannot solve this.
it should be impossible that apache is mixing vhost-special directives. i
can reproduce this on demand.
It's hard to tell which IP-based
On 21 Feb 2011, at 09:12, Lee Goddard wrote:
Dear Apache Users,
I have been looking at a problem for so many hours now that I think it has made
me blind.
The below configuration is intended to restrict access to /admin-cgi/ to members of the
group admin, which is defined in a plain text
Hi Apache users,
i like to do some basic authentication with a simple token which is
user:password via http get.
How can i get the token which come in via http get into the header with
Apache ?
Regards,
Michael
On 02/21/2011 02:42 PM, Michael Prieß wrote:
Hi Apache users,
i like to do some basic authentication with a simple token which is
user:password via http get.
How can i get the token which come in via http get into the header
with Apache ?
Try mod_headers:
Thanks for your fast response. Setting the header works already fine. But
the real problem is how can i get the parameter from
http://localhost:/?token=1337base64token
into the header.
My usecase is i have a service which run behind my Apache httpd in the
background that only support basic
On Mon, 21 Feb 2011 14:01:42 +0100
Lee lee...@gmail.com wrote:
The strange thing is, if I change the group file so that the line:
adminjr: adminjr1 adminjr2
instead reads:
adminj: adminjr1 adminjr2
then access is denied as expected.
The original config you posted had
On Mon, 21 Feb 2011 15:15:59 +0100
Michael Prieß mailingliste...@googlemail.com wrote:
Thanks for your fast response. Setting the header works already fine. But
the real problem is how can i get the parameter from
http://localhost:/?token=1337base64token
into the header.
mod_headers won't do
Hello Team,
I have configured apache to access directory through browser.
Whenever
i am trying to access directory using following url, i am getting
default page and unable to browse files and subdirectory under that
directory.
My configuration in httpd.conf file is as shown below.
Directory
Hi,
i doesn't need features like Base64-decoding. I have a RewriteMap which
contain all the Basic64 authentifications tokens which are equal with the
token that come over the uri.
Need only a simple solution to pass them from the uri query into the http
header.
Regards,
Michael
On 21/02/2011 15:24, Nick Kew wrote:
Are you sure you haven't confusedyourself into a mismatch between
your config and your groups file?
Unfortunately, have triple checked that.
Am now to check if, by some typographical fluke, I have passed group
parameters into the users' file, it's all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/21/2011 02:40 PM, Amol Puglia wrote:
Hello Team,
I have configured apache to access directory through browser.
Whenever i am trying to access directory using following url, i am
getting default page and unable to browse files and
Hi,
I am fairly new to apache. I just installed it from the repositories on my
Ubuntu 10.04 notebook so I will assume that it is the latest version (not even
sure how to check that).
I made a change to the default site in /etc/apache2/sites-available to change
the path for the default site to
Apache users:
I've boiled the example down, attempted to clarify, and re-posted it on
the debian-user mailing list:
http://lists.debian.org/debian-user/2011/02/msg02171.html
David
-
The official User-To-User support
The simple way is to use options indexes like this:
Directory /var/opt/webstack/apache2/2.2/htdocs/frontend
*options indexes*
/Directory
If the above doesn't work then try putting: *Options +Indexes*
Put the above in your httpd.conf, AND stop and restart the server for
changes to take
You need to add the file type in your httpd.conf. I suggest look for:
IfModule dir_module
# Insert file types here
/IfModule
Between the two tags above insertindex.phpand it should work.
You need to stop and restart the server for changes to take effect. If
you want the complete
On 21 Feb 2011, at 09:12, Lee Goddard wrote:
Dear Apache Users,
I have been looking at a problem for so many hours now that I think it has made
me blind.
The below configuration is intended to restrict access to /admin-cgi/ to members of the
group admin, which is defined in a plain text
On 22 Feb 2011, at 06:55, Lee wrote:
Have I misunderstood the PCRE engine, or is this a bug...?
Thou shalt not mix Directory and Location!
(the gory details are explained somewhere in the docs; I'm not
about to look it up).
Oh, and you clearly don't want PCRE or any *Match directive.
--
23 matches
Mail list logo
