XAP expires in half a day?

Question

I'm just wondering what could cause my xap to expire every half day (approximately). I mean, in the morning the user gets to the website and he uploads a copy of xap, by noon, if that user returns to the website and the website downloads another copy of xap for them.

I would hope that the only reason the user would need to download a new copy of xap would be when they clear their browser cache or ive will put a new copy on the server.

Any ideas on what would be the problem and fix it?

I ran fiddler on XAP boot and got the following lines from the cache tab of the xap boot record in the violin.

HTTP / 200 responses are cached by default if Expires, Pragma, or Cache-Control headers are not present and prohibit caching.

---

HTTP / 1.1 ETAG header present: "2ad1d6bfdd43cb1: 0" HTTP Last-Modified Header present: Tue, Aug 24 2010 22:43:19 GMT

There is no explicit HTTP expiration information. Most browsers use expiration heuristic policies: 10% delta between Last-Modified and Date is '02: 53: 34 ', so this answer will expire heuristically on 08/26/2010 4:39:26 PM.

---

Would this be a problem? Where to set explicit HTTP expiration?

Answer 1

The first thing to do: -

• Install a copy of Fiddler .
• Disable your temporary internet files.
• Launch Fiddler.
• Visit your host’s webpage.
• Find an HTTP session in a script that represents Xap download
• Add the headers of the original answer to your question above.

This will provide a very important set of clues to what the real problem is.

What happens when upgrading? Do you see the second XAP HTTP session returning a status response of 304? If you get 200, add the original Request headers for this second attempt and your original response headers to your question.

If you have 304, leave it for the appropriate amount of time, and then try again, let's still give the status 304? If you do not do the same as above.

These data will provide us with a lot of information to give a diagnosis.

Answer 2

I think HiTech Magic has hinted that you need to configure this setting in IIS. From what Fiddler said, it looks like your IIS does not have an expiration date for the content, which in my opinion is standard.

here's how to do it in IIS 6: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/0fc16fe7-be45-4033-a5aa-d7fda3c993ff.mspx?mfr=true here's how to do it in IIS 7 : h'ttp: //technet.microsoft.com/en-us/library/cc770661 (WS.10) .aspx

Answer 3

If you are using ASP.Net (can you edit the message to tell us what your backend is?), Try using Response.Cache. SetCacheability . There are some gotchas , tho.