Skip to content

Conversation

@N3uR0TiCV0iD
Copy link

This PR addresses issue #33.

Problem:

The current method of parsing a resource id in the parseId function uses the "@" symbol as a delimiter.

This causes issues when either the name of the resource or the vhost contains "@" symbols, leading to incorrect splitting and an error to be raised.

Solution:

Implemented percent encoding for "@" symbols found in the name/vhost when combining them as a "composite resource id".

Then, during parsing, we split the resource id and then apply percent decoding to retrieve the correct values.

This approach ensures accurate parsing while being backward compatible with existing resource IDs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants