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
Since Shlink version 4.0.0, URLs with schemas other than http or https have stopped working.
I created short url for viber://pa?chatURI=****. When attempting to open this short url, I receive a 500 response status.
In the Shlink logs, the following error is reported: Unsupported scheme "viber"; must be any empty string or in the set (http, https) in /etc/shlink/vendor/laminas/laminas-diactoros/src/Uri.php:476
This issue did not occur in previous versions, such as 3.7.4.
Expected behavior
When opening short url, I would like to receive a 302 response status, with location: viber://pa?chatURI=****
This behavior was in versions 3.7.4 and below
Minimum steps to reproduce
Create short url for viber://pa?chatURI=****
Open created short url
The text was updated successfully, but these errors were encountered:
Shlink used to have two very similar dependencies used to manipulate URIs, and I removed one of them as I could not remember the reason I was using a different one in one particular place. I guess this was the reason and there was a missing test to cover this case.
Shlink version
4.0.2
PHP version
?
How do you serve Shlink
Docker image
Database engine
PostgreSQL
Database version
16.2.0
Current behavior
Since Shlink version 4.0.0, URLs with schemas other than
http
orhttps
have stopped working.I created short url for
viber://pa?chatURI=****
. When attempting to open this short url, I receive a 500 response status.In the Shlink logs, the following error is reported:
Unsupported scheme "viber"; must be any empty string or in the set (http, https) in /etc/shlink/vendor/laminas/laminas-diactoros/src/Uri.php:476
Full stacktrace:
This issue did not occur in previous versions, such as 3.7.4.
Expected behavior
When opening short url, I would like to receive a 302 response status, with location: viber://pa?chatURI=****
This behavior was in versions 3.7.4 and below
Minimum steps to reproduce
viber://pa?chatURI=****
The text was updated successfully, but these errors were encountered: