Forum Discussion
5 Replies
- Prash_BharadwajAltocumulus
Maybe, you should try in other browsers.
If you have any iRule or any specific config for your site, you could try troubleshooting from there.
- Jay_Prasanth_13Nimbostratustried in all browsers , no luck . Any possibilities to disable cache through iRule?
- Jay_Prasanth_13Nimbostratus
This is my iRule ..,
if { [HTTP::uri] starts_with "/aa/bb-cc/dd/" } { set PREFIX_STATIC "/aa/bb-cc/dd" set XX_VAL [ getfield [HTTP::uri] "-" 2] set YY_VAL [ getfield [HTTP::uri] "-" 3] set ZZ_VAL [ getfield [HTTP::uri] "-" 4] set XX_NEW [split [lindex [split $XX_VAL /] end] -] HTTP::uri "$PREFIX_STATIC?q1=$XX_NEW&q2=$YY_VAL&q3=$ZZ_VAL" event disable }
- ArieAltostratus
Caching can indeed be a hindrance in troubleshooting, especially in Chrome. Disabling cache helps, but Chrome often doesn't seem to bypass all caching.
Browsers aren't the best app to troubleshoot iRules, although there are some plug-ins (like HTTP header monitors) that can be helpful. The developer modes in various browsers can also give you more information.
A much better tool to see what's going on are apps like Fiddler. However, browser cache could still affect the observations, as can active connections (as changes to iRules often don't take effect for existing connections).
cURL is probably one of the best options for quick troubleshooting. Although it's a Linux app, you can run it on Windows through apps like Cygwin.
Try something like this to see what's being returned:
curl -I http://www.domain.com/path
- ArieAltostratus
More thoughts.
-
Write informational data to the log file.
log local0.debug $var
-
Write informational data in the response.
HTTP::respond 200 content $var
-
Write informational data in to a custom header.
HTTP::header insert X-Info $var
-