Edge Functions
Running custom code during traffic processing
Last updated
Was this helpful?
Running custom code during traffic processing
Last updated
Was this helpful?
An Edge Function (EF) allow you to extend Link11 WAAP's tools and functionality. An EF consists of Lua code that can be run at different points in L11WAAP's traffic processing.
An EF can be configured to execute before any other processing occurs. Therefore, it can override or preempt other configured settings within L11WAAP. Or, it can be run after traffic filtering has been completed.
When an admin creates an Edge Function, L11WAAP validates the code with a Lua compiler. If any syntax errors are found, an error message will be shown. However, Link11 does not validate the code beyond this. Please ensure that the code is valid and tested before adding it. If the code has errors, undefined behavior can occur when L11WAAP attempts to execute it.
The main window (shown above) lists all current Edge Functions.
A name for this EF, to be used within the interface.
Information about this EF, for use within the interface.
This specifies when the Edge Function code will be executed.
Request: The EF will run as soon as L11WAAP receives an incoming request, before any other processing occurs.
Response: The EF will run as the last action before Link11 sends the response to the client.
The Lua code for the Edge Function.
Out of the box, L11WAAP includes a number of Edge Functions. Initially, they are not assigned to any .
Edge Functions are a very powerful tool. If you need assistance with this feature, please feel free to .
Edge Functions are assigned to destination paths/URLs within .
The administration (addition/deletion/editing/versioning) of EFs follows the conventions described .
