Forum Discussion

John_Ogle_45372's avatar
John_Ogle_45372
Icon for Nimbostratus rankNimbostratus
Jan 21, 2014

X-Cnection: close vs Connection: close

I'm having difficulty understanding the difference between these two. Article SOL6997 states:

 

"The X-Cnection: close header is also added to server-side connections utilizing an existing Keep-Alive connection if the client request included the Connection: close header. The BIG-IP uses the X-Cnection: close header to track client-side connections that want to close the connection after receiving a response through a virtual server utilizing the OneConnect feature."

 

Is the "X-Cnection: Close" header NOT an industry standard thing and just a technique that the LTM uses in place of the original/correct "Connection: closed" header? If so, does the origin webserver just ignore this field since it doesn't recognize the "X-Cnection: Close" header?

 

6 Replies

    • Erlend_123973's avatar
      Erlend_123973
      Icon for Nimbostratus rankNimbostratus
      But why does it even bother sending it? I am sure BigIP would be able close the client connection without it.
  • Why this header is sent back to the client? This should be kept local between the F5 and the server, shouldn't it?

     

  • NAG_65570's avatar
    NAG_65570
    Historic F5 Account

    as per K6997, while using OneConnect Transformations, X-Conection: close header is purely for BigIP internal tracking of client side connections which want to be closed after response is received.

     

    I believe, it is not being sent to client.

     

    It mean nothing to server though.

     

    • Daniel_Varela's avatar
      Daniel_Varela
      Icon for Employee rankEmployee

      That is my understanding as well but I saw it today doing some testing, when the response was a 403 that header came along. I will try to reproduce it again.