-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
1.1.2
-
None
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
mgnlExchangeWorkspaceName: website
mgnlExchangeRepositoryName: website
mgnlExchangeResourceMappingFile: resources5391325829615061113.xml
mgnlExchangeAction: activate
mgnlExchangeFilterRule: mgnl%3AcontentNode%2Cmgnl%3AmetaData%2Cmgnl%3Aresource%2C
mgnlExchangeNodeUUID: 95c6f51c-76f6-4cac-bf07-961943ec31e2
mgnlExchangeParentPath: %2F
....
- duplicates
-
MAGNOLIA-3327 Activation fails when activation from UTF-8 enabled instance to not UFT-8 enabled one
- Closed