Client connection getting reset on 304 Not Modified Response going through F5 Load Balancer

clients use HTTPS (SSL) channel to communicate with the Load Balancer, Load Balancer uses HTTP (Clear) channel to communicate with the server.

3-nodes round robin Port = 80 HTTP Profile = http SNAT Pool = Auto Map iRule assigned for http to https redirect Default Persistence Profile = source_addr

Does F5 adds since-last-modified on its own? What may be the reason for client connection getting reset.

F5 will not add last-modified headers unless you have additional profiles attached. You will need to check if the 304 message is actually being sent to the client. Use tcpdump and wireshark to confirm this.

Thanks will try to capture tcpdump. But the weird thing is it only happens when F5 is brought into picture and access server from firefox browser. When we access server without F5 in between it never happens.

Thanks will try to capture tcpdump. But the weird thing is it only happens when F5 is brought into picture and access server from firefox browser. When we access server without F5 in between it never happens.

Try removing the hdr

when HTTP_REQUEST_SEND {
clientside {
   if {[HTTP::header exists "If-Modified-Since"]}{
         HTTP::header remove "If-Modified-Since"
      }
   }
}

I’m surprised if it modifies any headers. It should just pass them through. A tcpdump capture client and serverside should confirm this.

clients use HTTPS (SSL) channel to communicate with the Load Balancer, Load Balancer uses HTTP (Clear) channel to communicate with the server.

3-nodes round robin Port = 80

HTTP Profile = http

SNAT Pool = Auto Map

iRule assigned for http to https redirect

Default Persistence Profile = source_addr

isn’t virtual server listening on port 443? is clientssl profile assigned to the virtual server?

also, i do think you need http to https redirect irule on this virtual server because it is listening on port 443.