Re: OWA 2000 mit Umlauten im Betreff
- From: "Heinz Mannheimer" <drtest23@xxxxxxxxxx>
- Date: Tue, 15 Nov 2005 16:01:56 +0100
Ich habe jetzt mal die ganze Urlscan.ini angehängt
[options]
UseAllowVerbs=1 ; if 1, use [AllowVerbs] section, else use
[DenyVerbs] section
UseAllowExtensions=0 ; if 1, use [AllowExtensions] section, else
use [DenyExtensions] section
NormalizeUrlBeforeScan=1 ; if 1, canonicalize URL before processing
VerifyNormalization=1 ; if 1, canonicalize URL twice and reject
request if a change occurs
AllowHighBitCharacters=1 ; if 1, allow high bit (ie. UTF8 or MBCS)
characters in URL
AllowDotInPath=1 ; if 1, allow dots that are not file
extensions
RemoveServerHeader=0 ; if 1, remove "Server" header from response
EnableLogging=1 ; if 1, log UrlScan activity
PerProcessLogging=0 ; if 1, the UrlScan.log filename will contain
a PID (ie. UrlScan.123.log)
AllowLateScanning=0 ; if 1, then UrlScan will load as a low
priority filter.
PerDayLogging=1 ; if 1, UrlScan will produce a new log each
day with activity in the form UrlScan.010101.log
RejectResponseUrl= ; UrlScan will send rejected requests to the
URL specified here. Default is /<Rejected-by-UrlScan>
UseFastPathReject=0 ; If 1, then UrlScan will not use the
RejectResponseUrl or allow IIS to log the request
; If RemoveServerHeader is 0, then AlternateServerName can be
; used to specify a replacement for IIS's built in 'Server' header
AlternateServerName=
[AllowVerbs]
;
; Note that these entries are effective if "UseAllowVerbs=1"
; is set in the [Options] section above.
;
GET
HEAD
POST
OPTIONS
SEARCH
POLL
PROPFIND
BMOVE
BCOPY
SUBSCRIBE
MOVE
PROPPATCH
BPROPPATCH
DELETE
BDELETE
MKCOL
UNSUBSCRIBE
SUBSCRIPTIONS
COPY
LOCK
UNLOCK
PUT
ACL
NOTIFY
[DenyVerbs]
;
; Note that these entries are effective if "UseAllowVerbs=0"
; is set in the [Options] section above.
;
[DenyHeaders]
;
; Request headers listed in this section will cause UrlScan to
; reject any request in which they are present.
;
; Headers should be listed in the form
; Header-Name:
;
[AllowExtensions]
;
; Extensions listed here are commonly used on a typical IIS server.
;
; Note that these entries are effective if "UseAllowExtensions=1"
; is set in the [Options] section above.
;
..asp
..cer
..cdx
..asa
..htm
..html
..txt
..jpg
..jpeg
..gif
;.idq
;.htw
;.ida
;.idc
;.shtm
;.shtml
;.stm
..htr
;.printer
[DenyExtensions]
;
; Extensions listed here either run code directly on the server,
; are processed as scripts, or are static files that are
; generally not intended to be served out.
;
; Note that these entries are effective if "UseAllowExtensions=0"
; is set in the [Options] section above.
;
; Deny executables that could run on the server
..exe
..bat
..cmd
..com
; Deny infrequently used scripts
..htw ; Maps to webhits.dll, part of Index Server
..ida ; Maps to idq.dll, part of Index Server
..idq ; Maps to idq.dll, part of Index Server
;.htr ; Maps to ism.dll, a legacy administrative tool
..idc ; Maps to httpodbc.dll, a legacy database access tool
..shtm ; Maps to ssinc.dll, for Server Side Includes
..shtml ; Maps to ssinc.dll, for Server Side Includes
..stm ; Maps to ssinc.dll, for Server Side Includes
..printer ; Maps to msw3prt.dll, for Internet Printing Services
; Deny various static files
..ini ; Configuration files
..log ; Log files
..pol ; Policy files
..dat ; Configuration files
;.asp
;.cer
;.cdx
;.asa
[DenyUrlSequences]
... ; Don't allow directory traversals
../ ; Don't allow trailing dot on a directory name
\ ; Don't allow backslashes in URL
% ; Don't allow escaping after normalization
& ; Don't allow multiple CGI processes to run on a single request
"Daniel Melanchthon [MSFT]" <danielme@xxxxxxxxxxxxxxxxxxxx> schrieb im
Newsbeitrag news:%2356Xple6FHA.636@xxxxxxxxxxxxxxxxxxxxxxx
> Heinz Mannheimer schrieb:
>> Hallo Norbert,
>>
>> Vielen Dank für Deine schnelle Antwort:
>>
>> Folgendes gibt mir UrlScan.log
>>
>> [11-14-2005 - 12:59:04] Client at 89.11.132.251: URL contains sequence
>> '..', which is disallowed. Request will be rejected. Site Instance='1',
>> Raw
>> URL='/exchange/user/Posteingang/AW:%20Herzlichen%20Dank%20f%C3%BCr%20Ihren%20Besuc%20h%20_xF8FF_%20Ein%20auf%20die%20M....EML'
>
> Dann schau doch mal in die URLScan.ini und kommentiere das Filtern von
> ".." aus. Dein Problem sind nicht die Umlaute, sondern die Sequenz "...".
> BTW: Habt Ihr URLScan einfach nur installiert oder auch speziell für
> Exchange konfiguriert:
>
> http://groups.google.com/groups?q=daniel+melanchthon+urlscan+exchange
>
> --
> .:Daniel Melanchthon:.
> Technologieberater - Exchange Server
> http://blogs.technet.com/dmelanchthon
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
.
- Follow-Ups:
- Re: OWA 2000 mit Umlauten im Betreff
- From: Daniel Melanchthon [MSFT]
- Re: OWA 2000 mit Umlauten im Betreff
- References:
- OWA 2000 mit Umlauten im Betreff
- From: Heinz Mannheimer
- Re: OWA 2000 mit Umlauten im Betreff
- From: Heinz Mannheimer
- Re: OWA 2000 mit Umlauten im Betreff
- From: Daniel Melanchthon [MSFT]
- OWA 2000 mit Umlauten im Betreff
- Prev by Date: Re: OWA 2000 mit Umlauten im Betreff
- Next by Date: Re: OWA 2000 mit Umlauten im Betreff
- Previous by thread: Re: OWA 2000 mit Umlauten im Betreff
- Next by thread: Re: OWA 2000 mit Umlauten im Betreff
- Index(es):
Relevant Pages
|