|
|
|
 |
|
 |
 |
|
 It is time to introduce the winners. The 2006 winners take iRules to an entirely new level of power and sophistocation. To the winners - congratulations! You are the best of the best. To all participants, we thank you for your participation. Please look forward to receiving your t-shirts and other prizes shortly. We would also like to thank our industry expert and F5 contest judges. Without your significant contribution of time, this contest would not be possible.
|
|
|
|
|
|
|
|
1st Place and Grand Prize Winner
Jamey Price (USA) - "reverseproxy_webmail_prod"
This iRule provides reverse-proxy functionality for a set of Lotus Notes 7 servers to provide webmail to end users. The results of developing this iRule were reduced configuration complexity as well as avoidance of previously unacceptable performance provided by alternative solutions. According to Jason Bloomberg, a contest judge and Senior Analyst with ZapThink, "The cookie manipulations make this iRule especially interesting."
2nd Place Winner
Kevin Stewart (USA) - "OCSP Authentication error redirect"
When clients fail OCSP authentication, secure web pages are usually replaced with a basic "Page cannot be displayed" error consisting of very little information to troubleshoot the error. This iRule helps users and reduces IT Help Desk workloads by generating dynamic HTML/CSS/Javascript that includes the specific error for further diagnosis. Judge Jason Rahm commented, "As a former helpdesk worker, THANK YOU! Ingenious use of error data to provide exactly the problem in the HTTP::response event helps keep support calls short and sweet."
3rd Place Winner
Jari Leppälä (Finland) - "Antispam"
Spam is a universal challenge for any organization. To reduce connections to backend servers that steal valuable processing cycles, this iRule detects and rejects sources opening large amounts of client connections in a short timeframe, which is often indicative of spam. It does so by counting SMTP connections from a specific IP address within a given timeframe. If an abusive IP client is detected, a message is sent to the email originator and they are added to an abusers list to block future attempts. "Handling spam at this stage can significantly cut down on network traffic," commented contest judge Zeus Kerravala. CLICK HERE to review these winning iRules.
1st Place and Grand Prize Winner
Jamey Price (USA) - "reverseproxy_webmail_prod"
This iRule provides reverse-proxy functionality for a set of Lotus Notes 7 servers to provide webmail to end users. The results of developing this iRule were reduced configuration complexity as well as avoidance of previously unacceptable performance provided by alternative solutions. According to Jason Bloomberg, a contest judge and Senior Analyst with ZapThink, "The cookie manipulations make this iRule especially interesting."
2nd Place Winner
Kevin Stewart (USA) - "OCSP Authentication error redirect"
When clients fail OCSP authentication, secure web pages are usually replaced with a basic "Page cannot be displayed" error consisting of very little information to troubleshoot the error. This iRule helps users and reduces IT Help Desk workloads by generating dynamic HTML/CSS/Javascript that includes the specific error for further diagnosis. Judge Jason Rahm commented, "As a former helpdesk worker, THANK YOU! Ingenious use of error data to provide exactly the problem in the HTTP::response event helps keep support calls short and sweet."
3rd Place Winner
Jari Leppälä (Finland) - "Antispam"
Spam is a universal challenge for any organization. To reduce connections to backend servers that steal valuable processing cycles, this iRule detects and rejects sources opening large amounts of client connections in a short timeframe, which is often indicative of spam. It does so by counting SMTP connections from a specific IP address within a given timeframe. If an abusive IP client is detected, a message is sent to the email originator and they are added to an abusers list to block future attempts. "Handling spam at this stage can significantly cut down on network traffic," commented contest judge Zeus Kerravala. CLICK HERE to review these winning iRules.
|
|
|
|
|
|
|
|
|
1st Place Winner
Sake Blok / Ion-IP B.V. (The Netherlands) - "iRule_Persist_On_HTTP_Data"
For SOAP-based authentication against LDAP servers and cached for performance optimization, traditional load balancing was not a viable alternative due to the burden large cache files placed on each server. By using this iRule to parse HTTP requests for Session-ID data and either persist the session to the originating server or create a new Session-ID, Ion-IPs customer was able to avoid a costly investment in larger servers to support this application. Added judge Rahm, "The extent to which traffic can be persisted is really shown off here. Nice work!"
2nd Place Winner
Nuno Paulino / Telindus Portugal (Portugal) - "w3c_iRule"
To support W3C logging formats with host-header validation, this ingenious iRule translates floating point values to strings and make appropriate conversions as string functions. In this case, it was translation of milliseconds to seconds. Judge Joe Pruitt commented, "You have to give credit when someone finds a unique solution to a known issue in one of your products. This iRule will be very useful to the community."
3rd Place Winner
Eduardo Saito / Assistec Integracao (Brazil) - "irule_limit_num_connections_googlebot"
While most websites desire regular crawling by leading search engines such as Google, many prefer to limit the number of server cycles consumed by the process. By utilizing connection limits for a known source IP address, this iRule protects server performance while still enabling crawling. It also helps manage this process from the network before the requests reach the servers. According to judge Pruitt, "This iRule enables a number of useful ways to limit connection rates for abusive clients." CLICK HERE to review these winning iRules.
1st Place Winner
Sake Blok / Ion-IP B.V. (The Netherlands) - "iRule_Persist_On_HTTP_Data"
For SOAP-based authentication against LDAP servers and cached for performance optimization, traditional load balancing was not a viable alternative due to the burden large cache files placed on each server. By using this iRule to parse HTTP requests for Session-ID data and either persist the session to the originating server or create a new Session-ID, Ion-IPs customer was able to avoid a costly investment in larger servers to support this application. Added judge Rahm, "The extent to which traffic can be persisted is really shown off here. Nice work!"
2nd Place Winner
Nuno Paulino / Telindus Portugal (Portugal) - "w3c_iRule"
To support W3C logging formats with host-header validation, this ingenious iRule translates floating point values to strings and make appropriate conversions as string functions. In this case, it was translation of milliseconds to seconds. Judge Joe Pruitt commented, "You have to give credit when someone finds a unique solution to a known issue in one of your products. This iRule will be very useful to the community."
3rd Place Winner
Eduardo Saito / Assistec Integracao (Brazil) - "irule_limit_num_connections_googlebot"
While most websites desire regular crawling by leading search engines such as Google, many prefer to limit the number of server cycles consumed by the process. By utilizing connection limits for a known source IP address, this iRule protects server performance while still enabling crawling. It also helps manage this process from the network before the requests reach the servers. According to judge Pruitt, "This iRule enables a number of useful ways to limit connection rates for abusive clients." CLICK HERE to review these winning iRules.
|
|
|
|
|
|
|