Forum Discussion

kridsana_52318's avatar
kridsana_52318
Icon for Nimbostratus rankNimbostratus
Feb 12, 2015

Oneconnect Profile and Ram cache feature conflict option

Hi

 

Let's me took this straight

 

From SOL10480 , It's said if cache is used then HTTP server side is transform to HTTP 1.0

 

and In oneconnect, It's transform HTTP 1.0 to HTTP 1.1

 

So If we using both feature (oneconnect profile and ram cache profile)

 

Is this conflict will make application not full functionable?

 

application delivery
availability
design
LTM

2 Replies

Sort By
  • StephanManthey's avatar
    StephanManthey
    Icon for MVP rankMVP
    Feb 12, 2015

    Hi teepan123,

     

    that´s not a conflict from my perspective.

     

    The solution mentions as well, that the http header "Connection: Keep-alive" will be inserted to allow persistent connections (aka keep-alive connections) between BIG-IP and pool members.

     

    Thanks, Stephan

     

  • TJ_Vreugdenhil's avatar
    TJ_Vreugdenhil
    Icon for Cirrus rankCirrus
    Feb 12, 2015

    Not sure if the following will help you as a workaround, but it's something I have used in the past.

    So anything in the DGL gets cached – the specific else CACHE::enable clause was added to support dynamic entries "/ops/images.ashx?imageid=".

     if {not ([class match $httpuri starts_with RAM_CACHE_URI_LIST-A])} { 
        CACHE::disable 
    } else { 
        CACHE::enable 
    } 


class RAM_CACHE_URI_LIST-A {
   {
      "/content/"
      "/ops/images.ashx?imageid="
      "/pa/"
   }
}