You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
First thanks for this very useful library.
We just met a problem due to purl upgrading from 1.1 to 1.2.
We have some scenarios with post requests like this one (including slashes) : And I make a POST request to "users/{{ENCODED_EMAIL}}/contents/{{CONTENT_B64URL_ENCODED}}"
It was working but we recently see that the slashes were replace by %2f.
This is a new feature of purl 1.2 which manages slashes in path_segment.
With purl 1.1 the behavior is like this :
Hi,
First thanks for this very useful library.
We just met a problem due to purl upgrading from 1.1 to 1.2.
We have some scenarios with post requests like this one (including slashes) :
And I make a POST request to "users/{{ENCODED_EMAIL}}/contents/{{CONTENT_B64URL_ENCODED}}"
It was working but we recently see that the slashes were replace by %2f.
This is a new feature of purl 1.2 which manages slashes in path_segment.
With purl 1.1 the behavior is like this :
With purl 1.2 the behavior is like this :
Regards,
Arnaud
The text was updated successfully, but these errors were encountered: