Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

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?

0
Rate this Question

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

It is a custom header added by the F5. The web server will ignore it.

0
Comments on this Answer
Comment made 23-Apr-2015 by Erlend 88
But why does it even bother sending it? I am sure BigIP would be able close the client connection without it.
0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hi, maybe it's too late to comment, but I found explanation of use case when the "X-Cnection" header might be used. It is for oneConnect Transformation, as stated in this SOL https://support.f5.com/csp/article/K6997

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Why this header is sent back to the client? This should be kept local between the F5 and the server, shouldn't it?

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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.

0
Comments on this Answer
Comment made 05-Jan-2018 by Daniel Varela 711

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.

0