[MGNLXAA-23] UTF-8 enabled encoding breaks activation process Created: 10/Nov/10 Updated: 10/Nov/10 Resolved: 10/Nov/10 |
|
| Status: | Closed |
| Project: | Transactional Activation |
| Component/s: | None |
| Affects Version/s: | 1.1.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Roelof Jan | Assignee: | Jan Haderka |
| Resolution: | Duplicate | 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When settings the config property "magnolia.utf8.enabled=true", BasicSyndicatorImpl on the author starts escaping HTTP headers for activation posts. The XAReceiveFilter on the public node does not honor this property likewise, resulting in an error when writing to an escaped repository path with "%2F" for every slash. One might wonder if encoding the headers under the prescribed condition is a very obvious choice. Outgoing headers: POST /magnoliaPublic/.magnolia/activation HTTP/1.1 |
| Comments |
| Comment by Jan Haderka [ 10/Nov/10 ] |
| Comment by Jan Haderka [ 10/Nov/10 ] |
|
What you need to do is to enable utf-8 on both of the instances at the same time. |