[MAGNOLIA-1655] Virtual URI mappings: handle parameters in toURI Created: 02/Aug/07 Updated: 25/Nov/13 Resolved: 22/Sep/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.1 M1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Boris Kraft |
| Resolution: | Obsolete | 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 |
|
If you map a destination URI to something like: toURI=/help/services.html?id=1233 it would be nice that the query string added would be parsed and parameters available in the destination page (just like with forwards - that can't unfortunately be used with magnolia pages). |
| Comments |
| Comment by Tobias Mattsson [ 22/Sep/11 ] |
|
It is possible to have toURI=forward:/help/services.html?id=1233 which will be handled by the filter chain, the forwarded to path is in AggregationState.currentURI and the parameters are set. |