infex
asked on
Reload of new page (RTF) gives old version
Hello,
I use windeows 2000 server with IIS and ASP. This works quite good.
However, some of the documents generated need to be printed in an exact way by the users. To have a full control over this proces, they are generated in RTF format.
We give them the extention .RTF or .DOC
We have set server extentions so that these formats are handled by the ASP interpreter.
Each time the document is called, it is (or should be) generated on the fly, including a time-stamp.
We set the appropriate settings so that if a user calls those documents, on his machine MS WORD opens and he can print from there.
We have one problem however. If we call the document with the same document name repeatedly, we have most of the time an old version.
We are sure there is no proxy between server and the client on which we test. On the client we make sure caching is off.
What can be done in order to make sure that every time the document is generated again and in the last version send to the clients.
I use windeows 2000 server with IIS and ASP. This works quite good.
However, some of the documents generated need to be printed in an exact way by the users. To have a full control over this proces, they are generated in RTF format.
We give them the extention .RTF or .DOC
We have set server extentions so that these formats are handled by the ASP interpreter.
Each time the document is called, it is (or should be) generated on the fly, including a time-stamp.
We set the appropriate settings so that if a user calls those documents, on his machine MS WORD opens and he can print from there.
We have one problem however. If we call the document with the same document name repeatedly, we have most of the time an old version.
We are sure there is no proxy between server and the client on which we test. On the client we make sure caching is off.
What can be done in order to make sure that every time the document is generated again and in the last version send to the clients.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This systems works.
However, we now want to work a different way : an ASP file is given the extention .DOC or .RTF
As we know only the RTF format, no matter which extention we give RTF is generated by the ASP upon calling.
We did set in IIS the necessary settings so that if through the web a file with extension .RTF is called, the concerning ASP page is handled by the ASP interpreter (even if it has the extention .RTF). So no file is made on the server.
The generated RTF is send to the browser, which sees it is to be handled by MS Word and displayed by word.
This goes the first time. However, we are not able to ensure that the users have always the last version.
Apparently we can not use a "response expires" in RTF. The problems seems to be located at the client side.
As the .RTF is in reality a .ASP file on the server side, we can not give it always an other name.
How make sure it is always correctly reloaded?