Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
Description
This leads to a couple of problems with test operating with UTF8-chars in the node name.
Note that the MagnoliaHttpClient does find such a node (on website workspace) - but the MagnoliaRestClient fails.
@Test @Fixture(fixtureFile = "website.ääööüü.yaml", repository = WEBSITE) void nodeExistsWorksForUTF8NodeNames(MagnoliaHttpClient magnoliaHttpClient) throws IOException { boolean nodeExistsAccordingToMagnoliaRestClient = client.nodeExists(WEBSITE, "/ääööüü"); int responseStatus = magnoliaHttpClient.get( magnoliaHttpClient.user(new User() { @Override public String getUserName() { return "superuser"; } @Override public String getPassword() { return "superuser"; } }).instance(Instance.DIRECT_AUTHOR).path("/ääööüü").build()).code(); boolean nodeExistsAccordingToMagnoliaHttpClient = 200 == responseStatus; assertEquals(nodeExistsAccordingToMagnoliaHttpClient, nodeExistsAccordingToMagnoliaRestClient); }
The above test fails.
While debugging & checking JCR-app. it becomes clear that
- website.ääööüü.yaml is bootstrapped properly.
- MagnoliaRestClient cannot find the node with nodeExists
- but the MagnoliaHttpClient does find the node.
The issue may be ther underlying reason for MGNLTEST-235
Checklists
Acceptance criteria
Attachments
Issue Links
- is caused by
-
MGNLREST-394 REST requests with Umlaut characters in URL fail
-
- Closed
-
- is related to
-
MGNLTEST-235 Cleanup fails to delete nodes with UTF8-chars in node-/file-name - failing silently!
-
- Closed
-