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
We just had one user adding https://foo.bar.org/ into the config, which didn't work because of the trailing slash and the origin being https://foo.bar.org.
We should either:
Validate the input somehow and show an error to the user, to make sure the origins are all in the correct format
Or allow this specific case and strip trailing slashes
(I kinda prefer (1) because it covers more cases)
Somewhat related, I wonder if we support explicit ports like http://foo.bar.org:80 in that case ?
The text was updated successfully, but these errors were encountered:
We just had one user adding
https://foo.bar.org/
into the config, which didn't work because of the trailing slash and the origin beinghttps://foo.bar.org
.We should either:
(I kinda prefer (1) because it covers more cases)
Somewhat related, I wonder if we support explicit ports like
http://foo.bar.org:80
in that case ?The text was updated successfully, but these errors were encountered: