[KB 19140功能解说] Internet Explorer 10不释放会话
[b]* 本文由赛捷软件（上海）有限公司翻译完成，未经授权不得转载。如需转载，请先联系相应版块的版主取得授权。[/b][b]产品[/b]
Sage X3
[b]国家[/b]
北美
[b]类别[/b]
配置
[b]描述[/b]
• IE10不释放会话。在IE 10浏览器中退出X3会话后，许可证仍滞留在用户监控任务中
o 受影响的操作系统和IE10版本如下：
o Windows 7 Enterprise : 6.1.7601 SP 1 Build 7601
IE 10.0.9200.16618
o Windows 8
IE 10.09200.16599
• 重现步骤：
1. 用IE10登录X3 web客户端
2. 退出web客户端
3. 再次启动X3，并前往用户监控功能（PSADX），注意到第一个用户仍显示登录在内
[b]原因[/b]
这是IE10的一个阻塞问题
[b]解决方法[/b]
[b]状态[/b]
正在等待Web服务器未来更新中出修复。
[b]变通方法[/b]
1. 退回IE9或使用以下变通方法。
2. 备份位于…\X3WEB\WebTools\SOFTS\HTTPD\conf下的httpd.conf文件
3. 停止Apache和Tomcat服务（SageX3 _ WEB _ apachehttpd _ X3WEB和SageX3_WEB_apachetomcat_X3WEB）
4. （用#号）对Sage X3 Web服务器嵌入在httpd.conf文件中的以下行进行注释，以停用安全模块。
#### Section ADONIX WEB SERVER - mod_security - systemtype=[windows]
#
# ATTENTION : File "mod_security2.so" must be present in modules folder.
#
# --- Load module "security"
#
# 16w_127 - Add module security pour apache 2.2
# Enable the module "mod_security2"
#LoadModule security2_module modules/mod_security2/mod_security2.so
# -- Rule engine initialization ----------------------------------------------
# Enable ModSecurity, attaching it to every transaction. Use detection
# only to start with, because that minimises the chances of post-installation
# disruption.
#
#SecRuleEngine On
# -- Request body handling ---------------------------------------------------
# Allow ModSecurity to access request bodies. If you don't, ModSecurity
# won't be able to see any POST parameters, which opens a large security
# hole for attackers to exploit.
#
#SecRequestBodyAccess On
# Maximum request body size we will accept for buffering. If you support
# file uploads then the value given on the first line has to be as large
# as the largest file you are willing to accept. The second value refers
# to the size of data, with files excluded. You want to keep that value as
# low as practical.
#
#SecRequestBodyLimit 13107200
#SecRequestBodyNoFilesLimit 131072
# Store up to 128 KB of request body data in memory. When the multipart
# parser reachers this limit, it will start using your hard disk for
# storage. That is slow, but unavoidable.
#
#SecRequestBodyInMemoryLimit 131072
# -- Response body handling --------------------------------------------------
# Allow ModSecurity to access response bodies.
# You should have this directive enabled in order to identify errors
# and data leakage issues.
#
# Do keep in mind that enabling this directive does increases both
# memory consumption and response latency.
#
#SecResponseBodyAccess On
# Which response MIME types do you want to inspect? You should adjust the
# configuration below to catch documents but avoid static files
# (e.g., images and archives).
#
#SecResponseBodyMimeType text/plain text/html text/xml
# Buffer response bodies of up to 512 KB in length.
# SecResponseBodyLimit 524288
# What happens when we encounter a response body larger than the configured
# limit? By default, we process what we have and let the rest through.
# That's somewhat less secure, but does not break any legitimate pages.
#
#SecResponseBodyLimitAction ProcessPartial
# -- Filesystem configuration ------------------------------------------------
# The location where ModSecurity stores temporary files (for example, when
# it needs to handle a file upload that is larger than the configured limit).
#
# This default setting is chosen due to all systems have /tmp available however,
# this is less than ideal. It is recommended that you specify a location that's private.
#
#SecTmpDir C:\SAGE\SAFEX3\WEBV1\X3WEB\WebData/TEMP/
# The location where ModSecurity will keep its persistent data. This default setting
# is chosen due to all systems have /tmp available however, it
# too should be updated to a place that other users can't access.
#
#SecDataDir C:\SAGE\SAFEX3\WEBV1\X3WEB\WebData/TEMP/
# -- File uploads handling configuration -------------------------------------
# The location where ModSecurity stores intercepted uploaded files. This
# location must be private to ModSecurity. You don't want other users on
# the server to access the files, do you?
#
#SecUploadDir C:\SAGE\SAFEX3\WEBV1\X3WEB\WebData/SERVERSLOGS/APACHE/uploads
# By default, only keep the files that were determined to be unusual
# in some way (by an external inspection script). For this to work you
# will also need at least one file inspection rule.
#
#SecUploadKeepFiles RelevantOnly
# Uploaded files are by default created with permissions that do not allow
# any other user to access them. You may need to relax that if you want to
# interface ModSecurity to an external program (e.g., an anti-virus).
#
#SecUploadFileMode 0600
# -- Debug log configuration -------------------------------------------------
# The default debug log configuration is to duplicate the error, warning
# and notice messages from the error log.
#
#SecDebugLog C:\SAGE\SAFEX3\WEBV1\X3WEB\WebData/SERVERSLOGS/APACHE/logs/modsec_debug.log
#secDebugLogLevel 4
# -- Audit log configuration -------------------------------------------------
# Log the transactions that are marked by a rule, as well as those that
# trigger a server error (determined by a 5xx or 4xx, excluding 404,
# level response status codes).
#
#SecAuditEngine RelevantOnly
#SecAuditLogRelevantStatus "^(?:5|4(?!04))"
# Log everything we know about a transaction.
#SecAuditLogParts ABIJDEFHZ
# Use a single file for logging. This is much easier to look at, but
# assumes that you will use the audit log only ocassionally.
#
#SecAuditLogType Serial
#SecAuditLog C:\SAGE\SAFEX3\WEBV1\X3WEB\WebData/SERVERSLOGS/APACHE/logs/modsec_audit.log
# Specify the path for concurrent audit logging.
#SecAuditLogStorageDir C:\SAGE\SAFEX3\WEBV1\X3WEB\WebData/SERVERSLOGS/APACHE/audit
# -- Miscellaneous -----------------------------------------------------------
# Use the most commonly used application/x-www-form-urlencoded parameter
# separator. There's probably only one application somewhere that uses
# something else so don't expect to change this value.
#
#SecArgumentSeparator &
# Settle on version 0 (zero) cookies, as that is what most applications
# use. Using an incorrect cookie version may open your installation to
# evasion attacks (against the rules that examine named cookies).
#
#SecCookieFormat 0
#
# Include RULES (NONE BY DEFAULT)
# All rules configuration files must contain "x3" String
#
#Include C:\SAGE\SAFEX3\WEBV1\X3WEB\WebData/_CUSTOMERS/HTTPD/MOD_SECURITY/rules/*x3*.conf
##
5. 启动Apache和Tomcat服务（SageX3 _ WEB _ apachehttpd _ X3WEB和SageX3_WEB_apachetomcat_X3WEB）
[b]缺陷标识[/b]
<P><SPAN style="COLOR: #1a1a1a"><SPAN style="FONT-STYLE: normal; FONT-FAMILY: segoe ui; COLOR: #1a1a1a; FONT-SIZE: 10pt; FONT-WEIGHT: normal; TEXT-DECORATION: none">74-11351</SPAN></SPAN> </P>
<P>SAM 90742</P>
页:
[1]