Bug fix | Storage service should support record ids with encoded %2F
Type of change
- Bug Fix
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
Does this introduce a change in the cloud provider implementation, if so which cloud?
Does this introduce a breaking change?
What is the current behavior?
SpringBoot by default disables certain special characters in the URL. These characters include encoded percent, semi-colon, back and front slashes and period. Not having support for encoded %2F in the URL is causing certain APIs such as GET /record/record:id to fail if the record id contains %2F.
What is the new/expected behavior?
Added conditional support for enabling encoded %2F in URL.
Have you added/updated Unit Tests and Integration Tests?
Integration Test - Yes