<< Click to Display Table of Contents >> Navigation:  Event and Object Analysis > Capture Results Filtering > Prefiltering HTTP Requests > Actions > JUMP Action

Continue processing an HTTP object in another table.

Description

This action continues processing an HTTP object in another table.

Format

<action name="jump" value="<table name>" />

The "name" attribute:

The name attribute specifies the name of the action: name="jump".

The value attribute:

The value="..." attribute specifies the name of the table to jump for the further processing of the object HTTP object.

Please note:
Jumping to the main table is prohibited to avoid loops.

Jumps, which can lead to an explicit or implicit recursion, are prohibited as well.

Example:

GET requests are passed for processing to the get-process table. GET requests are processed in the get-process table. ACCEPT for requests to win.mail.ru. Return to the main table for further processing.

<?xml version="1.0" encoding="utf-8"?>
<filter name="HTTP filter" version="1.0">
 <comment>HTTP filter.</comment>
 <table name="main">
   <rule enabled="1">
     <comment>
       Processing of GET requests is passed to the "get-process" table.
     </comment>
     <match>
       <c name="method" value="GET"/>
     </match>
     <action name="jump" value="get-process"/>
   </rule>
 
   <rule enabled="1">
     <action name="drop" />
   </rule>
 </table>
 
 <table name="get-process">
   <comment>
     GET requests are processed in the table get-process.
   </comment>
 
   <rule enabled="1">
     <comment>
       ACCEPT for requests for win.mail.ru.
     </comment>
     <match>
       <c name="req-header"
          headername="Host"
          op="eq"
          value="win.mail.ru" />
     </match>
     <action name="accept" />
   </rule>
 
   <rule enabled="1">
     <comment>
       Return to "main" table for further processing.
     </comment>
     <action name="return" />
   </rule>
 </table>
 
</filter>