I think that is what TS is code to, if you want changes, you need to talk dev@
if you send the first request without AE header, then you should get a response without encoding, the server may or may not have an encoded response, but we don't know that. so, another request with AE header, TS will do another try to the origin server, to see if you can get a encoded response. in your case, the answer is no, and the result is saved. but if you send the AE header in the first request, then you will get a response without encoding, which will satisfy the requests with or without AE header, so for the following requests TS will not try the origin server anymore. what is the problem here? looks like we have wasted some disk spaces etc. do we really need to cut that down? 在 2012-09-25二的 13:01 +0900，Kim, Sehoon写道： > * Our Environment > - ATS 3.0.4, 3.2.0 > > * In our environment, > Without Vary header response, Request Content-Type is image. > > - First Request > No Accept-Encoding header, alternative one is cached!! > > - Second Request > With Accept-Encoding header, another alternative is cached!! > > Is this the right operation? > > > And, > -First Request > With Accept-Encoding header, alternative one is cached!! > > - Second Request > I receive Cached Response!! > > How can I solve this issue? > > Thanks in advance > Seri > > > >
