From a08043caada8b9b31089a822981a555dc1a47bdd Mon Sep 17 00:00:00 2001
From: Daniel Earl Poirier The text/plain or text/html
-Description: Determines whether encoded path separators in URLs are allowed to
be passed through
+Syntax: AllowEncodedSlashes On|OffSyntax: AllowEncodedSlashes On|Off|NoDecodeDefault: AllowEncodedSlashes OffContext: server config, virtual host Status: Core
-Module: core
+Compatibility: Available in Apache 2.0.46 and later Compatibility: Available in Apache httpd 2.0.46 and later.
+NoDecode option available in 2.2.18 and later. AllowEncodedSlashes directive allows URLs
which contain encoded path separators (%2F for /
and additionally %5C for \ on according systems)
- to be used. Normally such URLs are refused with a 404 (Not found) error.
With the default value, Off, such URLs are refused
+ with a 404 (Not found) error.
With the value On, such URLs are accepted, and encoded
+ slashes are decoded like all other encoded characters.
With the value NoDecode, such URLs are accepted, but
+ encoded slashes are not decoded but left in their encoded state.
Turning AllowEncodedSlashes On is
mostly useful when used in conjunction with PATH_INFO.
Allowing encoded slashes does not imply decoding.
- Occurrences of %2F or %5C (only on
- according systems) will be left as such in the otherwise decoded URL
- string.
If encoded slashes are needed in path info, use of NoDecode is
+ strongly recommended as a security measure. Allowing slashes
+ to be decoded could potentially allow unsafe paths.
| Açıklama: | Apache HTTP Sunucusunda daima mevcut olan çekirdek özellikler |
|---|---|
| Durum: | Ãekirdek |