{"id":709,"date":"2012-05-23T14:54:50","date_gmt":"2012-05-23T12:54:50","guid":{"rendered":"http:\/\/hasselba.ch\/blog\/?p=709"},"modified":"2012-05-23T20:50:42","modified_gmt":"2012-05-23T18:50:42","slug":"controlling-the-http-expires-header","status":"publish","type":"post","link":"https:\/\/hasselba.ch\/blog\/?p=709","title":{"rendered":"Controlling the HTTP Expires Header"},"content":{"rendered":"

After reading a question on stack overflow<\/a> about setting an own HTTP expires header<\/a> and the problem that an additional header is generated automatically,\u00a0 I made some tests how the domino server can be forced to stop this behaviour programmatically.<\/p>\n

During my tests I was able to stop it by using\u00a0 facesContext.responseComplete()<\/em> but this works only for „headless“ XPages (set rendered <\/em>to false<\/em>).\u00a0If you are calling the method in a normal XPage (set rendered <\/em>to true<\/em>), the generated output will be discarded and looks like the „headless“ version.<\/p>\n

Here are two examples including screenshots from firebug console (containing the HTTP response):<\/p>\n