Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
documentation:latest:writingrulesand_headers [2020/05/06 10:51]
127.0.0.1 external edit
documentation:latest:writingrulesand_headers [2020/05/08 22:27] (current)
Line 32: Line 32:
 | Deny access to /config/ directory ​ |  <​nowiki>​^/​config/</​nowiki> ​ |  deny  | | Deny access to /config/ directory ​ |  <​nowiki>​^/​config/</​nowiki> ​ |  deny  |
 | Do not restrict /​public/ ​ |  <​nowiki>​^/​public/</​nowiki> ​ |  skip  | | Do not restrict /​public/ ​ |  <​nowiki>​^/​public/</​nowiki> ​ |  skip  |
 +| Do not restrict /skip/ and restrict other to authenticated users  |  <​nowiki>​^/​skip/</​nowiki> ​ | $ENV{REQUEST_URI} =~ /skip/ ? skip : 1 |
 | Makes authentication optional, but authenticated users are seen as such (that is, user data are sent to the app through HTTP headers) ​ |  <​nowiki>​^/​forum/</​nowiki> ​ |  unprotect ​ | | Makes authentication optional, but authenticated users are seen as such (that is, user data are sent to the app through HTTP headers) ​ |  <​nowiki>​^/​forum/</​nowiki> ​ |  unprotect ​ |
 | Restrict access to the whole site to users that have the LDAP description field set to "LDAP administrator"​ (must be set in exported variables) ​ |  default ​ |  <​html>​$description&​nbsp;​eq&​nbsp;"​LDAP&​nbsp;​administrator"</​html> ​ | | Restrict access to the whole site to users that have the LDAP description field set to "LDAP administrator"​ (must be set in exported variables) ​ |  default ​ |  <​html>​$description&​nbsp;​eq&​nbsp;"​LDAP&​nbsp;​administrator"</​html> ​ |
Line 110: Line 111:
 ===== Wildcards in hostnames ===== ===== Wildcards in hostnames =====
  
-{{..:​new.png?​direct&​35|}} Since 2.0, a wildcard can be used in virtualhost name (not in aliases !): ''​*.example.com''​ matches all hostnames that belong to ''​example.com''​ domain. Version 2.0.9 improves this and allows better wildcards such as ''​test-*.example.com''​+{{..:​new.png?​direct&​35|}} Since 2.0, a wildcard can be used in virtualhost name (not in aliases !): ''​*.example.com''​ matches all hostnames that belong to ''​example.com''​ domain. Version 2.0.9 improves this and allows better wildcards such as ''​test-*.example.com'' ​or ''​test-%.example.com''​. The ''​%''​ wilcard doesn'​t match subdomains.
  
 Even if a wildcard exists, if a virtualhost is explicitly declared, this rule is applied. Example with precedence order for test.sub.example.com:​ Even if a wildcard exists, if a virtualhost is explicitly declared, this rule is applied. Example with precedence order for test.sub.example.com:​
   - test.sub.example.com   - test.sub.example.com
 +  - test%.sub.example.com
   - test*.sub.example.com   - test*.sub.example.com
 +  - %.sub.example.com
   - *.sub.example.com   - *.sub.example.com
-  - *.example.com +  - *.example.com ​//​(''​%.example.com''​ does not match test.sub.example.com)//​