[MGNLFORM-93] Forms should exclude themselves from being cached Created: 24/May/11 Updated: 03/Apr/12 Resolved: 12/Jan/12 |
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | None |
| Affects Version/s: | 1.3.1 |
| Fix Version/s: | 1.3.2, 1.4 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Tobias Mattsson | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Description |
|
For 1.2.3 version A common problem with the multi step forms is that the first page needs to be excluded from caching. This is caused by the fact that the page contains a unique id, the form state token, which identifies the state kept on the server side. Subsequent steps can be cached since they carry the id as a request parameter and such requests aren't cached. |
| Comments |
| Comment by Philipp Bärfuss [ 07/Sep/11 ] |
|
Can only be solved in a good way by implementing |
| Comment by Philipp Bärfuss [ 02/Jan/12 ] |
|
Needs to be backported to 1.3.2 |
| Comment by Philipp Bärfuss [ 09/Jan/12 ] |
|
Please verify that this was commited to the branch too, there is no svn commit on the ticket. |