[MAGNOLIA-3327] Activation fails when activation from UTF-8 enabled instance to not UFT-8 enabled one Created: 19/Oct/10 Updated: 19/Jan/11 Resolved: 06/Jan/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.3.7 |
| Fix Version/s: | 4.4.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| 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)
|
||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
Target instance should be notified of the utf settings of the author so it can process content properly on activation or in the very least fail with more meaningful message the with permission check on non existent path. The problem occurs even when activating page that doesn't actually contain any special characters |
| Comments |
| Comment by Frank Rittinger [ 17/Dec/10 ] |
|
As discussed with Jan on the magnolia users mailing list, this issue still exists (magnolia 4.4.1 Enterprise on Ubuntu Linux 10.04 and Tomcat 6 and Java 6) if both instances run with UTF8 enabled. I checked on the filters, they are enabled and show up in the stack trace on the public instance. Activation works if UTF8 is disabled on both ends, though. Authoring: Public: |
| Comment by Zdenek Skodik [ 03/Jan/11 ] |
|
Reproduce-able with magnolia.utf8.enabled=true on both 4.4.1 Author&Public. |
| Comment by Jan Haderka [ 05/Jan/11 ] |
|
The activation issue when UTF-8 is enabled on both - author and public is dealt with in |
| Comment by Jan Haderka [ 06/Jan/11 ] |
|
The activation between instances with different UTF-8 setting is not allowed as it is not possible to ensure always the correct conversion in such case (decoding is transparent to the ReceiveFilter so filter would have to try to guess if the values were decoded or just match the string produced normally only for encoded character). |