Forum Discussion

cymru81's avatar
cymru81
Icon for Altocumulus rankAltocumulus
Sep 12, 2013

APM page cannot be displayed...

Hi, We are just initially setting up our Big IPs with APM license. We seem to be pretty much there with our policy etc. just we have noticed when we logout and then 'click here to open a new session' we constantly get a page cannot be displayed error. the only fix we can find is to clear the browser cache then re-visit the URL and all appears fine until next logout.

 

Anyone else experienced this or have a suggestion?

 

thanks!

 

5 Replies

  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus

    What's the browser? Are you behind a proxy? Do you have something like firebug or the equivalent to show what network connections and requests/responses are being made when you clink on the link?

     

  • The browser is IE10, ive also tried Firefox 12.0 and it behaves the same. Im going direct, and not behind a proxy. Umm I don't have firebug, is this free or is there an equal free equivalent?

     

  • If I may add, you can use Firebug, Fiddler, WireShark, IEWatch, HTTPWatch, and even tcpdump. The objective is to be able to observe the actual HTTP payload (not just what the browser is rendering).

     

    Also, do you have persistence set in the APM policy?

     

  • right, I am more familiar with some of them. I will run a capture, what would I be looking for?

     

    im not sure what persistence in the APM policy means, what does this mean and how do I check?

     

  • In the access policy configuration properties, on the "SSO / Auth Domains" tab, you should see three check boxes in the "Cookie Options" section.

     

    The Secure option sets the secure flag in the Set-Cookie header to the client. This tells the browser to only send the cookie back in a secure communication (vi HTTPS).

     

    The HTTP Only option sets the httponly flag in the Set-Cookie header to the client. This tells the browser to not allow script-based access to cookies, and can help prevent (slow down) some cross-site scripting attacks.

     

    The Persistent option sets the expires flag in the Set-Cookie header to the client and includes a date/time value. This causes the browser to store the cookie in the file system. If the option is not checked, the cookie is "session-based" and only resides in browser memory and is deleted when the browser closes.

     

    Now that I'm thinking about though, you're not closing the browser between sessions, so it's probably not a cookie thing. What you want to see in the capture is anything anomalous. I can't really say what that is until you've tried it. Also, do you see anything odd in the APM logs?