Abstract:
A system and method for selectively storing one or more web objects in a memory is disclosed. A server response is received at a network traffic management device, wherein the server response is associated with a client request sent from a client device and includes at least one web object. The server response is analyzed using a security module of the network traffic management device which determines if the at least a portion of the server response contains suspicious content in relation to one or more defined policy parameters handled by the security module. An instruction is sent from the security module to a cache module of the network traffic management device upon determining that the at least a portion of the server response contains suspicious information, wherein the cache module does not store the at least one web object upon receiving the instruction.

Description:
STATEMENT OF RELATED APPLICATION 
       [0001]    The present application claims the benefit of priority based on United States Provisional Patent Application Ser. No. 61/433,050, filed on Jan. 14, 2011, in the name of inventors Yuval Levy, Ron Talmor and Beni Serfaty, entitled “System and Method for Preventing Policy Violations From Being Stored in a RAM Cache”, all commonly owned herewith. 
     
    
     TECHNOLOGICAL FIELD 
       [0002]    This technology generally relates to network communication security that integrates security inspection solutions with network traffic acceleration solutions on a same network device. In particular, the technology relates to selectively storing web objects in a RAM cache memory in a network traffic management device based on policy decisions made by the network traffic management device. 
       BACKGROUND 
       [0003]    Existing firewalls utilize a memory or cache which stores web objects that are static in nature, such as pictures, audio, JavaScript and the like. This memory allows the firewall to operate more efficiently by allowing it to retrieve the stored web objects contained in server responses instead of having to repeatedly request such information from the servers in the secured network. This results in reducing network load and improving overall user experience. However, the memory and the firewall are not able to communicate with one another in an efficient manner, as will be discussed below. 
         [0004]    What is needed is a system and method which allows the firewall to communicate with the memory and instructs the memory such that memory does not store the web objects in the server responses if it is deemed that the client request is suspicious and/or if it is determined that the policy for the user has become non-stable. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0005]      FIG. 1  is a diagram of an example system environment that includes a network traffic management device in accordance with an aspect of the present disclosure; 
           [0006]      FIG. 2  is a block diagram of the network traffic management device shown in  FIG. 1  in accordance with an aspect of the present disclosure; 
           [0007]      FIG. 3  is an example flow chart diagram depicting portions of a process at least partially handled by the network traffic management device in accordance with the present disclosure; and 
           [0008]      FIG. 4  is an example flow chart diagram depicting portions of a process at least handled by the network traffic management device in accordance with the present disclosure. 
       
    
    
       [0009]    While these examples are susceptible of embodiment in many different forms, there is shown in the drawings and will herein be described in detail preferred examples with the understanding that the present disclosure is to be considered as an exemplification and is not intended to limit the broad aspect to the embodiments illustrated. 
       SUMMARY 
       [0010]    In an aspect, a method of selectively storing one or more web objects in a memory is disclosed. The method includes receiving a server response at a network traffic management device, wherein the server response is associated with a client request sent from a client device and includes at least one web object. The method includes analyzing the server response using a security module of the network traffic management device and determining if the at least a portion of the server response contains suspicious content in relation to one or more defined policy parameters handled by the security module. The method includes sending an instruction from the security module to a cache module of the network traffic management device upon determining that the at least a portion of the server response contains suspicious information, wherein the cache module does not store the at least one web object upon receiving the instruction. 
         [0011]    In an aspect, a non-transitory machine readable medium having stored thereon instructions for selectively storing one or more web objects in a memory. The medium includes machine executable code which, when executed by at least one machine, causes the machine to receive a server response from a server, wherein the server response is associated with a client request sent from a client device and includes at least one web object. The machine is configured to analyze the server response and determine if at least a portion of the server response is suspicious in relation to one or more defined policy parameters. The machine is configured to send an instruction to a cache module upon determining that the at least a portion of the server response is suspicious in relation to the one or more defined policy parameters, wherein the cache module does not store the at least one web object in a memory upon receiving the instruction. 
         [0012]    In an aspect, a network traffic management device comprises a network interface configured to receive and transmit client requests and server responses between at least one client device and at least one server over one or more networks. The network traffic management device includes a memory configured to store one or more programming instructions associated with selectively storing one or more web objects. network traffic management device includes one or more processors configured to execute the stored programming instructions, which when executed by the one or more processors, cause the one or more processors to analyze a received server response associated with a client request sent from a client device, wherein the server response includes at least one web object. The one or more processors is configured to determine if the at least a portion of the server response is suspicious in relation to one or more defined policy parameters. The one or more processors is configured to send an instruction to a cache module upon determining that the at least a portion of the server response is suspicious in relation to the one or more defined policy parameters, wherein the at least a portion of the server response is not stored in the memory as a result of the instruction. 
       DETAILED DESCRIPTION 
       [0013]      FIG. 1  is a diagram of an example system environment that includes a network traffic management device in accordance with an aspect of the present disclosure.  FIG. 1  illustrates an example system environment  100  which employs one or more network traffic management devices  110  capable of selectively storing web objects in a cache memory based on policy decisions made by the network traffic management device  110 . 
         [0014]    The example system environment  100  includes one or more Web and/or non Web application servers  102  (referred generally as “servers”), one or more client devices  106  and one or more network traffic management devices  110 , although the environment  100  could include other numbers and types of devices in other arrangements. The network traffic management device  110  is coupled to the servers  102  via local area network (LAN)  104  and client devices  106  via a wide area network  108 . Generally, client device requests are sent over the network  108  to one or more Web application servers  102  which are received or intercepted by the network traffic management device  110 . 
         [0015]    Client devices  106  comprise network computing devices capable of connecting to other network computing devices, such as network traffic management devices  110  and/or servers  102 . Such connections are performed over wired and/or wireless networks, such as network  108 , to send and receive data, such as for Web-based requests, receiving server responses to requests and/or performing other tasks. Non-limiting and non-exhausting examples of such client devices include personal computers (e.g., desktops, laptops), tablets, smart televisions, video game devices, mobile and/or smart phones and the like. In an example, client devices  106  can run one or more Web browsers that provide an interface for operators, such as human users, to interact with for making requests for resources to different web server-based applications and/or Web pages via the network  108 , although other server resources may be requested by client devices. One or more Web-based applications may run on one or more of the servers  102  that provide the requested data back as one or more server responses to the one or more network devices. 
         [0016]    The servers  102  comprises one or more server network devices or machines capable of operating one or more Web-based and/or non Web-based applications that may be accessed by other network devices (e.g. client devices, network traffic management devices) in the environment  100 . The servers  102  can provide web objects and other data representing requested resources, such as particular Web page(s), image(s) of physical objects, JavaScript and any other objects, that are responsive to the client devices&#39; requests. It should be noted that the servers  102  may perform other tasks and provide other types of resources. It should be noted that while only two servers  102  are shown in the environment  100  depicted in  FIG. 1 , other numbers and types of servers may be utilized in the environment  100 . 
         [0017]    It is also contemplated that one or more of the servers  102  may comprise a cluster of servers managed by one or more network traffic management devices  110 . In one or more aspects, the servers  102  may be configured implement to execute any version of Microsoft® IIS server, RADIUS server, DIAMETER server and/or Apache® server, although other types of servers may be used. Further, additional servers may be coupled to the network  108  and many different types of applications may be available on servers coupled to the network  108 . 
         [0018]    Network  108  comprises a publicly accessible network, such as the Internet, which is connected to client devices  106 . However, it is contemplated that the network  108  may comprise other types of private and public networks that include other devices. Communications, such as requests from clients  106  and responses from servers  102 , take place over the network  108  according to standard network protocols, such as the HTTP, UDP and/or TCP/IP protocols in this example. However, the principles discussed herein are not limited to this example and can include other protocols. Further, it should be appreciated that network  108  may include local area networks (LANs), wide area networks (WANs), direct connections and any combination thereof, as well as other types and numbers of network types. On an interconnected set of LANs or other networks, including those based on differing architectures and protocols, routers, switches, hubs, gateways, bridges, cell towers and other intermediate network devices may act as links within and between LANs and other networks to enable messages and other data to be sent from and to network devices. Also, communication links within and between LANs and other networks typically include twisted wire pair (e.g., Ethernet), coaxial cable, analog telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links and other communications links known to those skilled in the relevant arts. In essence, the network  108  includes any communication method by which data may travel between client devices  106 , Web application servers  102  and network traffic management device  110 , and the like. 
         [0019]    LAN  104  comprises a private local area network that allows communications between the one or more network traffic management devices  110  and one or more servers  102  in the secured network. It is contemplated, however, that the LAN  104  may comprise other types of private and public networks with other devices. Networks, including local area networks, besides being understood by those skilled in the relevant arts, have already been generally described above in connection with network  108  and thus will not be described further. 
         [0020]    As per the TCP/IP protocols, requests from the requesting client devices  106  may be sent as one or more streams of data packets over network  108  to the network traffic management device  110  and/or the servers  102 . Such protocols can be utilized by the client devices  106 , network traffic management device  110  and the servers  102  to establish connections, send and receive data for existing connections, and the like. It is to be understood that the one or more servers  102  may be hardware and/or software, and/or may represent a system with multiple servers that may include internal or external networks. 
         [0021]    As shown in the example environment  100  depicted in  FIG. 1 , the network traffic management device  110  is interposed between client devices  106  with which it communicates with via network  108  and servers  102  in a secured network with which it communicates with via LAN  104 . Again, the environment  100  could be arranged in other manners with other numbers and types of devices. Also, the network traffic management device  110  is coupled to network  108  by one or more network communication links and intermediate network devices (e.g. routers, switches, gateways, hubs and the like) (not shown). It should be understood that the devices and the particular configuration shown in  FIG. 1  are provided for exemplary purposes only and thus are not limiting. 
         [0022]    Generally, the network traffic management device  110  manages network communications, which may include one or more client requests and server responses, via the network  108  between the client devices  106  and one or more of the servers  102 . Client requests may be destined for one or more servers  102  and may take the form of one or more data packets sent over the network  108 . The client requests pass through one or more intermediate network devices and/or intermediate networks, until they ultimately reach the one or more network traffic management devices  110 . In any case, the network traffic management device  110  may manage the network communications by performing several network traffic related functions involving the communications. Some functions include, but are not limited to, load balancing, access control, and validating HTTP requests using JavaScript code that are sent back to requesting client devices  106 . 
         [0023]    Although examples of the server  102 , the network traffic management device  110 , and the client devices  106  are described and illustrated herein, each of the computers of the system  100  could be implemented on any suitable computer system or computing device. It is to be understood that the example devices and systems of the system  100  are for exemplary purposes, as many variations of the specific hardware and software used to implement the system  100  are possible, as will be appreciated by those skilled in the relevant art(s). In addition, two or more computing systems or devices may be substituted for any one of the devices in the system  100 . Accordingly, principles and advantages of distributed processing, such as redundancy, replication, and the like, also can be implemented, as desired, to increase the robustness and performance of the devices of the system  100 . 
         [0024]      FIG. 2  is a block diagram of the network traffic management device shown in  FIG. 1  in accordance with an aspect of the present disclosure. As shown in  FIG. 2 , an example network traffic management device  110  includes one or more device processors  200 , one or more device I/O interfaces  202 , one or more network interfaces  204 , and one or more device memories  218 , which are coupled together by bus  208 . In an aspect, the network traffic management device  110  includes one or more cache modules  206  and one or more security modules  210  that can be within the device memory  218  or outside device memory  218 . It should be noted that the network traffic management device  110  can be configured to include other types and/or numbers of components and is thus not limited to the configuration shown in  FIG. 2 . 
         [0025]    In an aspect, the network traffic management device  110  operates as a virtual server or proxy in the environment  100  between the requesting client devices  106  and the one or more destination servers  102 . In an aspect, the network traffic management device  110  intercepts and processes requests sent from the client device  106 , whereby the network traffic management device  110  is configured to transmit or forward the processed requests to the destination server  102 . Similarly, responses to the client requests are sent from the server  102 , whereby the network traffic management device  100  intercepts and processes the response to the client device  106  to perform the novel processes described in more detail below. 
         [0026]    Device processor  200  of the network traffic management device  110  comprises one or more microprocessors configured to execute computer/machine readable and executable instructions stored in the device memory  218 . Such instructions, when executed by one or more processors  200 , implement general and specific functions of the network traffic management device  110 . In addition, the instructions, when executed, implement the security module  210  to perform one or more portions of the novel processes described in more detail below. It is understood that the processor  200  may comprise other types and/or combinations of processors, such as digital signal processors, micro-controllers, application specific integrated circuits (“ASICs”), programmable logic devices (“PLDs”), field programmable logic devices (“FPLDs”), field programmable gate arrays (“FPGAs”), and the like. The processor  200  is programmed or configured according to the teachings as described and illustrated herein. 
         [0027]    Device I/O interfaces  202  comprise one or more user input and output device interface mechanisms. The interface may include a computer keyboard, mouse, display device, and the corresponding physical ports and underlying supporting hardware and software to enable the network traffic management device  110  to communicate with other network devices in the environment  100 . Such communications may include accepting user data input and providing user output, although other types and numbers of user input and output devices may be used. Additionally or alternatively, as will be described in connection with network interface  204  below, the network traffic management device  110  may communicate with the outside environment for certain types of operations (e.g., configuration) via one or more network management ports. 
         [0028]    Network interface  204  comprises one or more mechanisms that enable the network traffic management device  110  to engage in network communications over the LAN  104  and the network  108  using one or more of a number of protocols, such as TCP/IP, HTTP, UDP, RADIUS and DNS. However, it is contemplated that the network interface  204  may be constructed for use with other communication protocols and types of networks. Network interface  204  is sometimes referred to as a transceiver, transceiving device, or network interface card (NIC), which transmits and receives network data packets to one or more networks, such as the LAN  104  and the network  108 . In an example, where the network traffic management device  110  includes more than one device processor  200  (or a processor  200  has more than one core), each processor  200  (and/or core) may use the same single network interface  204  or a plurality of network interfaces  204 . Further, the network interface  204  may include one or more physical ports, such as Ethernet ports, to couple the network traffic management device  110  with other network devices, such as servers  102 . Moreover, the interface  204  may include certain physical ports dedicated to receiving and/or transmitting certain types of network data, such as device management related data for configuring the network traffic management device  110  or client request/server response related data. 
         [0029]    Bus  208  may comprise one or more internal device component communication buses, links, bridges and supporting components, such as bus controllers and/or arbiters. The bus  208  enables the various components of the network traffic management device  110 , such as the processor  200 , device I/O interfaces  202 , network interface  204 , and device memory  218 , to communicate with one another. However, it is contemplated that the bus  208  may enable one or more components of the network traffic management device  110  to communicate with components in other devices as well. Example buses include HyperTransport, PCI, PCI Express, InfiniBand, USB, Firewire, Serial ATA (SATA), SCSI, IDE and AGP buses. However, it is contemplated that other types and numbers of buses may be used, whereby the particular types and arrangement of buses will depend on the particular configuration of the network traffic management device  110 . 
         [0030]    Device memory  218  comprises computer readable media, namely computer readable or processor readable storage media, which are examples of machine-readable storage media. Computer readable storage/machine-readable storage media may include volatile, nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information. Such storage media includes computer readable/machine-executable instructions, data structures, program modules, or other data, which may be obtained and/or executed by one or more processors, such as device processor  200 . Such instructions, when executed, allow or cause the processor  200  to perform actions, including implementing an operating system for controlling the general operation of network traffic management device  110  to manage network traffic, implementing the security module  210  and the cache module  206  to perform one or more portions of the process discussed below. 
         [0031]    Examples of computer readable storage media include RAM, BIOS, ROM, 
         [0032]    EEPROM, flash/firmware memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the information, which can be accessed by a computing or specially programmed device, such as the network traffic management device  110 . 
         [0033]    Security module  210  is depicted in  FIG. 2  as being within memory  218  for exemplary purposes only; and it should be appreciated the module  210  may be alternatively located elsewhere. The security module  210  performs the processing and analyses of the requests/responses between the client device  106  and the server  102  to determine whether the requests/responses comply with or violate established or staging policy rules between the client device  106  and the server  102 . As will be discussed in more detail below, the security module  210  communicates with the cache module  206  to ensure that the cache module  206  selectively stores web objects in server responses that are deemed by the security module  210  to comply with established policies and/or are not deemed to be suspicious. 
         [0034]    In general, the network traffic management device  110  is configured to allow communication between the security module  210  and the cache module  206 , in which the security module  210  instructs the cache module  206  when a response and/or the contents in the response (e.g. web objects) are not to be stored. In an aspect, the security module  210  processes the contents of the response received from the server  102  to determine whether the transaction, such as a request and a response violates a security policy and/or whether the response contains suspicious content or is needed for further transaction. If the security module  210  determines that the response does violate the security policy for the client device  106 , contains suspicious content, needs further transactions enforcements, or its policy is not found to be stabilized yet, the security module  210  will inform the RAM cache  210  not to store the response and its contents. Some examples of actions which would violate a security policy include, but are not limited to, requests or responses that have triggered a violation (e.g. learn alarm, block staging); requests to pages that have triggered tightening suggestions (e.g. file types, URLs, and the like); the security module itself blocking a page; and pages that are within a restricted flow access. An example of a response that may be needed for further transaction enforcement is a page that has extractions configured. 
         [0035]    In an aspect, the network traffic management device  110  may be configured to allow the cache module  206  to completely clear its memory when the security module  210  deems that the security policy should change. This may occur when the legitimacy of the entire security policy may have been compromised (e.g. the web site is changed) or other scenario. In this aspect, the network traffic management device  110  will send an in-band command to the cache module  206  which instructs the cache module  206  to clear the contents of all the previously stored web objects and other data. In an aspect, it is contemplated that the network traffic management device  110  may send an out-of-band command to the cache module  206  to instruct the cache module  206  to clear the contents of all previously stored responses and web objects. 
         [0036]    The network traffic management device  110  may be configured such that the cache module  206  will by default automatically store each response and its contents unless the security module  210  instructs it not to store the response. It is contemplated, alternatively, that the network traffic management device  110  may be configured such that the cache module  206  will only store a response and its contents if the security module  210  instructs it to do so. 
         [0037]      FIG. 3  illustrates an example flow chart in accordance with a process between a requesting client device and the network traffic management device  110  described in accordance with an aspect of the present disclosure. In the example, a client device  106  sends a request via the network  108  to access a web page containing one or more web objects from one or more servers  102  in the secured network (Start Block). As shown in  FIG. 3 , the client request is received by the network traffic management device  110  (Block  300 ). Upon receiving the request, the network traffic management device  110  will determine whether a response containing the data (e.g. web page, web object) associated with the request is already stored in the cache module  206  of the network traffic management device  110  (Block  302 ). If the response is found to have been previously stored in the cache memory  206 , the stored response along with the requested data is retrieved from the cache memory  206  (Block  304 ). The network traffic management device  110  then sends the retrieved response to the client device  106  (Block  306 ), whereby the process then ends until another request is received (Block  308 ). 
         [0038]    Referring back to Block  302 , if the network traffic management device  110  determines that the requested information is not stored in the cache module  206 , the security module  210  examines and analyzes the client request (Block  310 ). Upon examining and analyzing the client request, the security module  210  will determine whether the request includes suspicious content (Block  312 ). If not, the network traffic management device  110  forwards the request to the appropriate server  102  (Block  314 ). As shown in  FIG. 3 , the process then proceeds to the steps described in  FIG. 4  (Block A). 
         [0039]    In an aspect, the network traffic management device  110  will store, preferably in the memory  218 , whether or not the client request contains suspicious content. As will be discussed in  FIG. 4 , this stored information may be used by the security module  210  in examining the server&#39;s response to determine whether the response may be legitimately sent from the server in response to a malicious request. 
         [0040]    Returning to Block  312  in  FIG. 3 , in examining and analyzing the client request, if the security module  210  determines that the client request appears to include suspicious content, the security module&#39;s  210  actions will depend on whether the security module  210  is operating in a blocking mode or a non-blocking mode. If the security module  210  is operating in the blocking mode, the network traffic management device  110  will block the client request and will not transmit the request to the server  102  (Block  320 ). Additionally, the network traffic management device  110  will send a response message (“blocked response message”) to the client device  106  informing it that the request has been blocked (Block  320 ). Additionally, the security module  210  will instruct the cache module  206  not to store the blocked page sent to the client device  106  (Block  322 ). The process then ends until another request is received (Block  324 ). 
         [0041]    Referring back to Block  318 , if the security module  210  is not operating in the blocking mode when examining the request, the network traffic management device  110  will forward the request to the server  102 . Additionally, the network traffic management device  110  will not to store the request in memory (Block  326 ). The process then ends until another request is received (Block  328 ). 
         [0042]      FIG. 4  is an example flow chart diagram depicting portions of the communication processes between the server and the client device via the network traffic management device in accordance with an aspect of the present disclosure. In particular,  FIG. 4  illustrates the process which occurs after the client request has been sent from the network traffic management device  110  to the server  102  (Block A). The server  102 , after processing the request, sends a response back to the requesting client device  106 , whereby the response is received by the network traffic management device  110  (Block  400 ). The security module  210  of the network traffic management device  110  examines and analyzes the response (Block  402 ) and determines whether it includes content or web objects that may be considered suspicious per policy parameters (Block  404 ). 
         [0043]    Per Block  404 , if the security module  210  does not find any suspicious content in the server response, the security module  210  will check the network traffic management device&#39;s  110  internal memory  218  for information that indicates that the client device&#39;s  106  request was initially found to contain suspicious content when it was passed onto the server (Block  406 ). This information would have been stored by the security module  210  if the network traffic management device  110  was not operating in a blocking mode when suspicious content was found in the client&#39;s request (Block  326  in  FIG. 3 ). 
         [0044]    If the security module  210  finds that the originating request was found to contain suspicious content, the security module  210  will proceed with forwarding the response to the client device  106  (Block  408 ). However, as shown in Block  408 , the security module  210  will instruct the cache module  206  not to store the response or any web objects in the response (Block  408 ). As mentioned above, the cache module  206  is configured to store web objects that can be quickly retrieved and sent to the client device in response to client requests for those web objects (see Blocks  302 ,  304 ,  306 ,  308  in  FIG. 3 ). Thus, the network traffic management device  110  maintains security by preventing the cache module  206  from storing suspicious web objects if the originating request was found to be suspicious. 
         [0045]    Referring back to Block  406 , if the security module  210  determines that no information of the request is stored in the internal memory  218 , the security module will proceed with transmitting the server&#39;s response to the client device  106  (Block  410 ). Additionally, the cache module  206  will automatically store the response as well as the web object(s) in the response (Block  412 ) since the security module  210  will have concluded that the policy rules for the request are stable and that the request and response are deemed safe per the policy parameters. The process then ends until another server response is received by the network traffic management device  110  (Block  424 ). 
         [0046]    Referring back to Block  404 , if the security module  210  determines that the server&#39;s  102  response contains suspicious content, the security module&#39;s  210  subsequent actions will depend on whether the security module  210  is operating in the blocking mode or non-blocking mode for that particular client request (Block  414 ). If the security module  210  is not operating in the non-blocking mode, the security module  210  instructs the cache module  206  not to store the response or any web objects in the response (Block  416 ) as the response is being sent to the requesting client device  106 . The network traffic management device  110  will then send the server&#39;s response to the client device  106  without storing the response nor its contents in the cache module  206  (Block  418 ). The process then ends until another server response is received by the network traffic management device  110  (Block  426 ). 
         [0047]    Referring back to Block  414  of  FIG. 4 , if the security module  210  is operating in a blocking mode when the response is received, the security module  210  will block the server&#39;s response by sending a blocked response page to the client device  106  (Block  420 ). In particular, the blocked response page informs the client device  106  that the page has been blocked and that the request cannot be honored (Block  420 ). Additionally, the security module  210  will instruct the cache module  206  not to store the blocked page in the manner described above (Block  422 ). The process then ends until another server response is received by the network traffic management device  110  (Block  428 ). 
         [0048]    Having thus described the basic concepts, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested hereby, and are within the spirit and scope of the examples. Additionally, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes to any order except as may be specified in the claims.