Faulty link generation when creating entities with string key and slashes

[dankaiser1808]

Assemblies affected

Microsoft.AspNetCore.OData Version 7.7.4 and also 8.2.5 Issue

Describe the bug

A change made a while ago in the Web API Framework has led to an issue where the link generation for entities with string keys that contain slashes is faulty. The problematic change (affects version 7.7.4) can be found in this pull request.

As a temporary workaround, we have replaced the ODataRoute class with a patched version of the class. In this patched class, the problematic code has been commented out (line 77-101 of the mentioned pull request).

Reproduce steps

• Create an entity with a string key that contains a slash
• Get request to the location header URL
• results in a 404 error because it interprets the unencoded slash as a path separator

Expected behavior

For the individual segments of a link or a URI, targeted escaping should be performed, especially in the case when a primary key or an entity ID contains a slash (or similarly problematic special characters).

Thank you for taking the time to review this issue. I look forward to your feedback and am ready to assist further if needed.

[ElizabethOkerio]

duplicate of: OData/AspNetCoreOData#1212. Will be tracked from the other repo