NO-Caching certain files with BIP

In our experience with HTTP clients and servers, we have not come across any that are intentionally sensitive to the ordering of non-duplicate headers in the request or response.

 

 

If I were to make a guess, I think the problem *might* be related to the HTTP/1.0 response from the server in the second instance. To explain, the Cache-Control directive is explicitly an RFC2616 directive, and HTTP/1.0 clients should not be expected to understand it. As an interim workaround, HTTP server vendors added the "Pragma: no-cache" directive. However, pragmas are advisory, not mandatory. RFC2616 section 14.32 goes so far as to say:

 

 

 

Note: because the meaning of "Pragma: no-cache as a response

 

header field is not actually specified, it does not provide a

 

reliable replacement for "Cache-Control: no-cache" in a response

 

 

 

So the question I have is whether the client (a) ignores Pragma: no-cache, and (b) ignores Cache-Control: directives coming back from an HTTP/1.0 server.

 

 

Can you run your test so that the response through the BIG-IP comes back as an HTTP/1.1 response?