ALT Linux Sisyphus discussions
 help / color / mirror / Atom feed
From: Aleksey Avdeev <solo@solin.spb.ru>
To: ALT Linux Sisyphus discussion list <sisyphus@lists.altlinux.org>
Subject: Re: [sisyphus] Apache SSLRequireSSL priority
Date: Thu, 22 Mar 2007 16:22:03 +0300
Message-ID: <460282FB.20200@solin.spb.ru> (raw)
In-Reply-To: <20070322053856.2c3fe539.bga@altlinux.org>

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

Grigory Batalov пишет:
> Здравствуйте!
> 
> А что, директива SSLRequireSSL имеет какой-то приоритет перед её
> окружающими? Я её запрятал в LimitExcept GET:
> 
> <Location /test>
>         <LimitExcept GET>
>                 <IfDefine SSL>
>                         SSLRequireSSL
>                 </IfDefine>
>         </LimitExcept>
> </Location>
> 
> Открываю http://localhost/test/ и вижу Forbidden.
> 
> access_log (как раз GET):
> 127.0.0.1 - - [22/Mar/2007:05:32:21 +0300] "GET /test/ HTTP/1.0" 403 1064
> 
> error_log:
> [Thu Mar 22 05:32:21 2007] [error] [client 127.0.0.1] access to /var/www/apache2/html/test/ failed, reason: SSL connection required

  После прочнения
<http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslrequiressl> и
<http://httpd.apache.org/docs/2.2/mod/core.html#limit> -- вознипло
устойчевое подозрение, что так и должно быть...

  Темболие, что в <http://httpd.apache.org/docs/2.2/mod/core.html#limit>
есть упомание, что <Limit>/<LimitExcept> могут неоказывать эффекта (2
абзац итаты):

Access controls are normally effective for all access methods, and this
is the usual desired behavior. **In the general case, access control
directives should not be placed within a <Limit> section.**

The purpose of the <Limit> directive is to restrict the effect of the
access controls to the nominated HTTP methods. For all other methods,
the access restrictions that are enclosed in the <Limit> bracket will
have **no effect**.

-- 

С уважением. Алексей.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

      reply	other threads:[~2007-03-22 13:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  2:38 Grigory Batalov
2007-03-22 13:22 ` Aleksey Avdeev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=460282FB.20200@solin.spb.ru \
    --to=solo@solin.spb.ru \
    --cc=sisyphus@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Sisyphus discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
		sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
	public-inbox-index sisyphus

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sisyphus


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git