精华内容
下载资源
问答
  • 语言:Deutsch,English,Français DHL选择要跟踪。 通过contextmenu直接将您带到您需要的信息。 你经常在互联网上买东西吗? 您是否对将跟踪ID从交货确认邮件中复制粘贴到DHL网站感到烦恼? 此扩展使此问题成为过去!...
  • Efficiency and Privacy Enhancement for a Track and Trace System of RFID-based Supply Chains
  • DHL选择跟踪。直接通过contextmenu获取所需的信息。 您经常在互联网上购买商品吗?您是否对将跟踪ID从交货确认邮件中复制粘贴到DHL网站感到烦恼?此扩展使此问题成为过去!右键单击选定的跟踪ID:上下文菜单条目可...
  • NVT: HTTP Debugging Methods (TRACE/TRACK) Enabled References cve: CVE-2003-1567 cve: CVE-2004-2320 cve: CVE-2004-2763 cve: CVE-2005-3398 cve: CVE-2006-4683 cve: CVE-2007-3008 cve: CVE-2008-7253 cve: ...

    漏洞报告显示:
    Medium (CVSS: 5.8)
    NVT: HTTP Debugging Methods (TRACE/TRACK) Enabled
    References
    cve: CVE-2003-1567 cve: CVE-2004-2320 cve: CVE-2004-2763 cve: CVE-2005-3398 cve: CVE-2006-4683 cve: CVE-2007-3008 cve: CVE-2008-7253 cve: CVE-2009-2823 cve: CVE-2010-0386 cve: CVE-2012-2223 cve: CVE-2014-7883
    bid: 9506
    bid: 9561
    bid: 11604
    Summary
    The remote web server supports the TRACE and/or TRACK methods. TRACE and TRACK are HTTP methods which are used to debug web server connections.
    Solution:
    Solution type: Mitigation
    Disable the TRACE and TRACK methods in your web server con guration. Please see the manual of your web server or the references for more information
    漏洞解决:根据建议关闭‘TRACE and TRACK methods ’
    处理方法:Apache版本大于2.2,在httpd.conf末尾添加:
    TraceEnable off
    1.查看Apache版本:httpd -v
    版本信息大于2.2
    2.在httpd.conf末尾添加TraceEnable off
    TraceEnable off
    3.验证

    展开全文
  • HTTP TRACE / TRACK Methods Allowed 漏洞修复

    万次阅读 2016-04-27 17:37:06
    在httpd.conf添加TraceEnable off

    这里写图片描述

    在httpd.conf添加

    TraceEnable off

    这里写图片描述

    展开全文
  • alert and trace

    2014-03-18 18:36:11
    Monitoring Errors with Trace Files and the Alert Log Each server and background process can write ...

    Monitoring Errors with Trace Files and the Alert Log

    Each server and background process can write to an associated trace file. When an internal error is detected by a process, it dumps information about the error to its trace file. Some of the information written to a trace file is intended for the database administrator, and other information is for Oracle Support Services. Trace file information is also used to tune applications and instances.

    Note:

    Critical errors also create incidents and incident dumps in the Automatic Diagnostic Repository. See Chapter 9, "Managing Diagnostic Data" for more information.

    The alert log is a chronological log of messages and errors, and includes the following items:

    • All internal errors (ORA-00600), block corruption errors (ORA-01578), and deadlock errors (ORA-00060) that occur

    • Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements

    • Messages and errors relating to the functions of shared server and dispatcher processes

    • Errors occurring during the automatic refresh of a materialized view

    • The values of all initialization parameters that had nondefault values at the time the database and instance start

    Oracle Database uses the alert log to record these operations as an alternative to displaying the information on an operator's console (although some systems also display information on the console). If an operation is successful, a "completed" message is written in the alert log, along with a timestamp.

    The alert log is maintained as both an XML-formatted file and a text-formatted file. You can view either format of the alert log with any text editor or you can use the ADRCI utility to view the XML-formatted version of the file with the XML tags stripped.

    Check the alert log and trace files of an instance periodically to learn whether the background processes have encountered errors. For example, when the log writer process (LGWR) cannot write to a member of a log group, an error message indicating the nature of the problem is written to the LGWR trace file and the alert log. Such an error message means that a media or I/O problem has occurred and should be corrected immediately.

    Oracle Database also writes values of initialization parameters to the alert log, in addition to other important statistics.

    The alert log and all trace files for background and server processes are written to the Automatic Diagnostic Repository, the location of which is specified by the DIAGNOSTIC_DEST initialization parameter. The names of trace files are operating system specific, but each file usually includes the name of the process writing the file (such as LGWR and RECO).

    See Also:

    • Chapter 9, "Managing Diagnostic Data" for information on the Automatic Diagnostic Repository.

    • "Alert Log" for additional information about the alert log.

    • "Viewing the Alert Log"

    • Oracle Database Utilities for information on the ADRCI utility.

    • Your operating system specific Oracle documentation for information about the names of trace files

    Controlling the Size of Trace Files

    You can control the maximum size of all trace files (excluding the alert log) using the initialization parameter MAX_DUMP_FILE_SIZE, which limits the file to the specified number of operating system blocks. To control the size of an alert log, you must manually delete the file when you no longer need it. Otherwise the database continues to append to the file.

    You can safely delete the alert log while the instance is running, although you should consider making an archived copy of it first. This archived copy could prove valuable if you should have a future problem that requires investigating the history of an instance.

    Controlling When Oracle Database Writes to Trace Files

    Background processes always write to a trace file when appropriate. In the case of the ARCn background process, it is possible, through an initialization parameter, to control the amount and type of trace information that is produced. This behavior is described in "Controlling Trace Output Generated by the Archivelog Process". Other background processes do not have this flexibility.

    Trace files are written on behalf of server processes whenever critical errors occur. Additionally, setting the initialization parameter SQL_TRACE = TRUE causes the SQL trace facility to generate performance statistics for the processing of all SQL statements for an instance and write them to the Automatic Diagnostic Repository.

    Optionally, you can request that trace files be generated for server processes. Regardless of the current value of the SQL_TRACE initialization parameter, each session can enable or disable trace logging on behalf of the associated server process by using the SQL statement ALTER SESSION SET SQL_TRACE. This example enables the SQL trace facility for a specific session:

    ALTER SESSION SET SQL_TRACE TRUE;
    

    Use the DBMS_SESSION or the DBMS_MONITOR packages to control SQL tracing for a session.

    Caution:

    The SQL trace facility for server processes can cause significant system overhead resulting in severe performance impact, so you should enable this feature only when collecting statistics.

    See Also:

    • Chapter 9, "Managing Diagnostic Data" for more information on how the database handles critical errors, otherwise known as "incidents."

    Reading the Trace File for Shared Server Sessions

    If shared server is enabled, each session using a dispatcher is routed to a shared server process, and trace information is written to the server trace file only if the session has enabled tracing (or if an error is encountered). Therefore, to track tracing for a specific session that connects using a dispatcher, you might have to explore several shared server trace files. To help you, Oracle provides a command line utility program, trcsess, which consolidates all trace information pertaining to a user session in one place and orders the information by time.

    See Also:

    Oracle Database Performance Tuning Guide for information about using the SQL trace facility and using TKPROF and trcsess to interpret the generated trace files

    Monitoring Database Operations with Server-Generated Alerts

    A server-generated alert is a notification from the Oracle Database server of an impending problem. The notification may contain suggestions for correcting the problem. Notifications are also provided when the problem condition has been cleared.

    Alerts are automatically generated when a problem occurs or when data does not match expected values for metrics, such as the following:

    • Physical Reads Per Second

    • User Commits Per Second

    • SQL Service Response Time

    Server-generated alerts can be based on threshold levels or can issue simply because an event has occurred. Threshold-based alerts can be triggered at both threshold warning and critical levels. The value of these levels can be customer-defined or internal values, and some alerts have default threshold levels which you can change if appropriate. For example, by default a server-generated alert is generated for tablespace space usage when the percentage of space usage exceeds either the 85% warning or 97% critical threshold level. Examples of alerts not based on threshold levels are:

    • Snapshot Too Old

    • Resumable Session Suspended

    • Recovery Area Space Usage

    An alert message is sent to the predefined persistent queue ALERT_QUE owned by the user SYS. Oracle Enterprise Manager reads this queue and provides notifications about outstanding server alerts, and sometimes suggests actions for correcting the problem. The alerts are displayed on the Enterprise Manager Database Home page and can be configured to send email or pager notifications to selected administrators. If an alert cannot be written to the alert queue, a message about the alert is written to the Oracle Database alert log.

    Background processes periodically flush the data to the Automatic Workload Repository to capture a history of metric values. The alert history table and ALERT_QUE are purged automatically by the system at regular intervals.

    来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/26844646/viewspace-1124383/,如需转载,请注明出处,否则将追究法律责任。

    转载于:http://blog.itpub.net/26844646/viewspace-1124383/

    展开全文
  • 我们在Chrome开发者工具里调试的时候,有时...其实,我们只需要在console控制台里,输入console.trace: 这里打印的callstack是可以复制粘贴的: ctrl v到本地即可: 更多Jerry的原创文章,尽在:“汪子熙”: ...

    我们在Chrome开发者工具里调试的时候,有时需要把函数执行的调用堆栈信息保存到本地以便进一步处理:

    然而Call stack列表下的数据无法复制粘贴。
    其实,我们只需要在console控制台里,输入console.trace:

    这里打印的callstack是可以复制粘贴的:

    ctrl v到本地即可:

    更多Jerry的原创文章,尽在:“汪子熙”:

    展开全文
  • Export and Import Trace Data

    2017-06-12 10:17:00
    导出和导入跟踪数据Export and Import Trace Data 仪器提供多种方法来导出和导入数据,用于合并、存档、仪器内部分析和通过其他工具进行外部分析。Instruments offers a variety of ways to export and import data...
  • Apache服务器关闭TRACE Method请求方式

    千次阅读 2016-10-26 10:07:17
    我们知道TRACETRACK是用来调试web服务器连接的HTTP方式.支持该方式的服务器存在跨站脚本漏洞,通常在描述各种浏览器缺陷的时候,把”Cross-Site-Tracing”简称为XST. 攻击者可以利用此漏洞欺骗合法用户并得到他们的...
  • WPF开发教程

    万次阅读 多人点赞 2019-07-02 23:13:20
    ------WPF开发教程 目录 WPF基础入门....... 1. WPF基础之体系结构......2. WPF基础之XAML....3. WPF基础之基元素......4. WPF基础之属性系统......5. WPF基础之路由事件......6. WPF基础之布局系统......7. WPF基础之样式设置和模板...
  • logback集成方式: %d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %thread [%mdc{MSGID}] %X{traceId} %logger{50} %file:%method:%line - %msg%n (一)基于Filter、HandlerInterceptor过滤器方式 import org.apache....
  • Oracle EBS Forms查看trace file

    千次阅读 2016-06-27 14:15:44
     ‘Regular Trace’ gives the least information andTrace with Binds and Waits’ (level 12) gives maximum information. Be careful while enabling SQL trace with wait and binds as this will make the ...
  • Ref: http://msdn2.microsoft.com/en-us/library/aa751795.aspx This topic describes the format of trace data, how to view it, and approaches that use the Service Trace Viewer to troubleshoot your applica...
  • 使用隐含Trace参数诊断Oracle Data Pump(expdp)故障 Data Pump数据泵是Oracle从10g开始推出的,用于取...
  • 最近公司搞新项目,需要使用FreeRTOS,之前只有Linux的基础(学了个皮毛),对于...在官网转悠的时候发现了有个可视化分析工具:FreeRTOS+Trace,感觉应该不错!下载后发现其是http://percepio.com/这个网站上的东西
  • 启用 HTTP TRACE 方法

    万次阅读 2012-04-11 16:10:11
    RFC 2616 for HTTP 如下定义 TRACE 方法,“此方法用于调用已请求消息的远程、应用层回送(loopback)。请求的接收方是源服务器或第一个代理或接收请求中零(0)Max-Forwards
  • trace && pprof

    2020-12-14 22:43:08
    It’s not appropriate if you want to track down slow functions, or generally find where your program is spending most of its CPU time. For that you should usego tool pprof, which shows the percentage...
  • Complete list of Microsoft SQL Server trace flags (585 trace flags)REMEMBER: Be extremely careful with trace flags, test in your test environment first. And consult professionals first if you are the ...
  • TRACE (VC)

    2018-10-30 19:26:23
    1、TRACETRACK是用来调试web服务器连接的HTTP方式。 2、TRACE宏对于VC下程序调试来说是很有用的东西,有着类似printf的功能。 3、MATLAB函数,用于求二维方阵的迹,即该方阵对角线上元素之和。4、Flex中的调试信息...
  • trace

    2011-10-18 16:15:46
    TRACETRACK是用来调试web服务器连接的HTTP方式。  支持该方式的服务器存在跨站脚本漏洞,通常在描述各种浏览器缺陷的时候,把"Cross-Site-Tracing"简称为XST。  攻击者可以利用此漏洞欺骗合法用户并得到...
  • Spring Security and Angular

    千次阅读 2018-07-06 11:20:29
    Spring Security and AngularA Secure Single Page ApplicationIn this tutorial we show some nice features of Spring Security, Spring Boot and Angular working together to provide a pleasant and secure use...
  • 【recommend】Tracing in .NET and Implementing Your Own Trace Listeners By Mansoor Ahmed Siddiqui reship from http://www.15s
  • Oracle event trace types

    2014-06-28 22:56:37
    Oracle event trace types 转自 dba-oracle Note: Here are related Oracle 10046 trace file notes: ?Types of Oracle trace events ?Displaying Oracle Trace Event files ?Create Oracle Trace file ...
  • Tracing in .NET and Implementing Your Own Trace ListenersBy Mansoor Ahmed Siddiqui Rating: 4.4 out of 5Rate this article print this article email this article to a colleague s...
  • The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and ...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 10,078
精华内容 4,031
关键字:

andtracetrack