You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We often face the following problem:
When we submit an xml file to sign, the file is showing correctly in the
browser, but when we sign it and it posts the results back to our target
url, we often get the result of a previous post back. If we just hit the
back button in IE then it posts again but with the correct values. Also if
we disable caching in IE everything is working fine.
Isn't it possible to prevent that page from being cached? By adding a
header or something like that?
Original issue reported on code.google.com by goo...@com2web.be on 10 May 2010 at 12:33
The text was updated successfully, but these errors were encountered:
The post-response.xhtml page is using the template.xhtml, which already has the
following to prevent page caching:
<meta http-equiv="expires" content="0" />
<meta http-equiv="cache-control" content="no-cache, no-store" />
<meta http-equiv="pragma" content="no-cache" />
Original comment by frank.co...@gmail.com on 13 Aug 2010 at 3:39
Ok, thanks. An additional question: I've read somewhere that
https://www.e-contract.be/ is your personal development server. Is that correct
and if so, are there plans to setup a production environment? (So we don't have
to maintain the application, because we are not familiar with linux and java)
Original comment by goog...@com2web.be on 13 Aug 2010 at 7:47
FedICT will have its own production environment. Unfortunately this service
will not be available for commercial usage, i.e. it will only be offered as a
service towards the public sector. If you want, I can help you setting up a
production ready eID DSS. Drop me a message at info@frankcornelis.be about the
details of your requirements for such a service so I can guide you a bit.
Original comment by frank.co...@gmail.com on 18 Aug 2010 at 12:06
Original issue reported on code.google.com by
goo...@com2web.be
on 10 May 2010 at 12:33The text was updated successfully, but these errors were encountered: