Mike,
I still think you misunderstand what's going on. Let's say you have a flash form (<cfform format="flash">) that posts to a page that doesn't contain a flash form. Theoretically the flash form is populating the content area of the http request with the data and passing it as a POST type request. At least that is what the browser thinks is happening (hence the warning). When you refresh the post request the browser re-issues the POST from the request history - that would be agnostic of the flash form - the browser sees an http request, not a "flash form", like the one below: ----------------- POST myFormHandler.cfm HTTP/1.1 Content-Type: text/html Referer: User-Agent: Mozilla/4.0 Host: mydomain.com Content-Length: 512 &postdata& ----------------------------- At least that is what I think should be happening. Perhaps there is something special in the flash form data that is "expiring" the data - an indicater to the CF server to ignore a second post. If so that would be a useful feature (as you suggest) IF it were something a developer can configure and control. Mark A. Kruger, CFG, MCSE www.cfwebtools.com www.necfug.com http://mkruger.cfwebtools.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:205187 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
