Forum Discussion

  • You are going to have to supply some more information as we don't have in depth knowledge of JRUN errors. What protocol are you running this over (HTTP, custom, etc)? What signifies an error? Is it a protocol level status code like and HTTP 500 error? Or is it something in the payload that you need to parse out? iRules makes it very easy to search response content but you have to know what you are looking for first. Text streams are easier, binary streams are doable as well but a bit more tricky to write.

     

     

    If you provide all the details as to the protocol you are using as well as what signifies an error, we will be able to guide you in the right direction.

     

     

    -Joe
  • So you are looking for error codes in the connection from the client to the server? Usually error codes are responses from the servers. If this is the case, you can do a HTTP::collect in the HTTP_REQUEST event. This will trigger the HTTP_REQUEST_DATA event to be called when the system has collected the specified amount of data from the client. You can then access the HTTP::payload and search as you would with any other string.

     

     

    How and what you set the collect size to depends on what protocol the error is coming across on. With HTTP, you can use the Content-Length header (if it exists).

     

     

    Please verify that the error does indeed come from the client (the request) and not the server (the response) and we can provide you a snippet of code to do the work. Or you could just search the forums for HTTP::collect and you'll find some examples yourself.

     

     

    -Joe
  • The errors come from the server, if the application is too busy. I will search the forums and view some of the examples.

     

     

    Thanks

     

     

  • So it's not in the request but in the response. Check out this thread for an example of examining the HTTP Response's payload.

     

     

    http://devcentral.f5.com/default.aspx?tabid=28&forumid=5&postid=3410&view=topic (Click here)

     

     

    -Joe